Virtualenv: AttributeError: module 'virtualenv.activation.python' has no attribute 'PestythonActivator'
I think it's just a typo in the latest release...
fj-sanchez
All 21 comments
Definitely something wrong, this change has broken pipenv for my projects!
derek-bo-derek
on 12 Jun 2020
Same, this was a breaking change in a patch version.
pascal-de-ladurantaye
on 12 Jun 2020
Likewise broke all the builds. Looks like issue identified and fixed in pull request. Lets hope it gets merged into master and built asap
andrewboss
on 12 Jun 2020
Introduced in #1855, which was merged without review and with nearly all checks failing.
GPHemsley
on 12 Jun 2020
Should we merge the fix without a review then? ;)
pascal-de-ladurantaye
on 12 Jun 2020
when can we know if it gets fixed, and how can i download the new version? im trying to do a virtualenv project but i get the same error
Pasha-t34
on 12 Jun 2020
when can we know if it gets fixed, and how can i download the new version? im trying to do a virtualenv project but i get the same error
Use pip install virtualenv==20.0.21 to return to the previous version.
joekohlsdorf
on 12 Jun 2020
Another confirmation of breakage from me. It broke all of my production build pipelines.
brutimus
on 12 Jun 2020
I have the same issue
anybody fixed it ?
tarp20
on 12 Jun 2020
I want to blame pipenv for failing to freeze its dependencies but that was a patch version (still, pipenv should freeze its dependencies)
pascal-de-ladurantaye
on 12 Jun 2020
Can we just rename PythonActivator to PestythonActivator? That just sounds better IMO
minhio
on 12 Jun 2020
pip uninstall virtualenv==20.0.22
pip install virtualenv==20.0.21
it is ok for now for me
d-demirci
on 12 Jun 2020
Use
pip install virtualenv==20.0.21to return to the previous version.
To future-proof, I'd recommend pip install 'virtualenv!=20.0.22'.
GPHemsley
on 12 Jun 2020
馃悰馃悕
josephong
on 12 Jun 2020
I have the same issue
anybody fixed it ?
the reply from joekohlsdorf helps a lot
Pasha-t34
on 12 Jun 2020
pip uninstall virtualenv==20.0.22
pip install virtualenv==20.0.21it is ok for now for me
My broken built is on the Travis side, it runs tox, is there a way to pin the virtualenv version in that case?
Cheukting
on 12 Jun 2020
Seems the devs fixed it now, panic over.
Cheukting
on 12 Jun 2020
So sorry, messed up that release earlier (馃う), should be all fine now with 20.0.23.
gaborbernat
on 12 Jun 2020
Version 20.0.23 works fine :+1:
fernandochimi-noverde
on 12 Jun 2020
"leftpad grade issue" :-(
jsbueno
on 12 Jun 2020
I want to blame pipenv for failing to freeze its dependencies
ahh, the irony.
petergaultney
on 14 Jun 2020
Related issues
schlamar
路
4Comments
elfosardo
路
3Comments
asottile
路
6Comments
jwarren116
路
5Comments
LeonSpors
路
6Comments
Most helpful comment
So sorry, messed up that release earlier (馃う), should be all fine now with
20.0.23.