Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AttributeError: module 'virtualenv.activation.python' has no attribute 'PestythonActivator' #1857

Closed
fj-sanchez opened this issue Jun 12, 2020 · 21 comments · Fixed by #1858
Closed
Labels

Comments

@fj-sanchez
Copy link

I think it's just a typo in the latest release...

@ghost
Copy link

ghost commented Jun 12, 2020

Definitely something wrong, this change has broken pipenv for my projects!

@pascal-de-ladurantaye
Copy link

Same, this was a breaking change in a patch version.

@neongazer
Copy link

Likewise broke all the builds. Looks like issue identified and fixed in pull request. Lets hope it gets merged into master and built asap

@GPHemsley
Copy link

Introduced in #1855, which was merged without review and with nearly all checks failing.

@pascal-de-ladurantaye
Copy link

Should we merge the fix without a review then? ;)

@jgrigorian23
Copy link

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

@joekohlsdorf
Copy link

joekohlsdorf commented Jun 12, 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.

@sstoops
Copy link

sstoops commented Jun 12, 2020

Another confirmation of breakage from me. It broke all of my production build pipelines.

@tarp20
Copy link

tarp20 commented Jun 12, 2020

I have the same issue

anybody fixed it ?

@pascal-de-ladurantaye
Copy link

I want to blame pipenv for failing to freeze its dependencies but that was a patch version (still, pipenv should freeze its dependencies)

@minhio
Copy link

minhio commented Jun 12, 2020

Can we just rename PythonActivator to PestythonActivator? That just sounds better IMO

@d-demirci
Copy link

pip uninstall virtualenv==20.0.22
pip install virtualenv==20.0.21

it is ok for now for me

@GPHemsley
Copy link

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'.

@josephong
Copy link

🐛🐍

@jgrigorian23
Copy link

I have the same issue

anybody fixed it ?

the reply from joekohlsdorf helps a lot

rrooij added a commit to terminusdb/terminusdb-client-python that referenced this issue Jun 12, 2020
@Cheukting
Copy link

pip uninstall virtualenv==20.0.22
pip install virtualenv==20.0.21

it 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
Copy link

Seems the devs fixed it now, panic over.

@gaborbernat
Copy link
Contributor

So sorry, messed up that release earlier (🤦), should be all fine now with 20.0.23.

@fernandochimi-noverde
Copy link

Version 20.0.23 works fine 👍

@jsbueno
Copy link

jsbueno commented Jun 12, 2020

"leftpad grade issue" :-(

@petergaultney
Copy link

petergaultney commented Jun 14, 2020

I want to blame pipenv for failing to freeze its dependencies

ahh, the irony.

@pypa pypa locked as resolved and limited conversation to collaborators Jun 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.