I think it's just a typo in the latest release...
Definitely something wrong, this change has broken pipenv for my projects!
Same, this was a breaking change in a patch version.
Likewise broke all the builds. Looks like issue identified and fixed in pull request. Lets hope it gets merged into master and built asap
Introduced in #1855, which was merged without review and with nearly all checks failing.
Should we merge the fix without a review then? ;)
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
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.
Another confirmation of breakage from me. It broke all of my production build pipelines.
I have the same issue
anybody fixed it ?
I want to blame pipenv for failing to freeze its dependencies but that was a patch version (still, pipenv should freeze its dependencies)
Can we just rename PythonActivator to PestythonActivator? That just sounds better IMO
pip uninstall virtualenv==20.0.22
pip install virtualenv==20.0.21
it is ok for now for me
Use
pip install virtualenv==20.0.21
to return to the previous version.
To future-proof, I'd recommend pip install 'virtualenv!=20.0.22'
.
🐛🐍
I have the same issue
anybody fixed it ?
the reply from joekohlsdorf helps a lot
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?
Seems the devs fixed it now, panic over.
So sorry, messed up that release earlier (🤦), should be all fine now with 20.0.23
.
Version 20.0.23
works fine :+1:
"leftpad grade issue" :-(
I want to blame pipenv for failing to freeze its dependencies
ahh, the irony.
Most helpful comment
So sorry, messed up that release earlier (🤦), should be all fine now with
20.0.23
.