ModuleNotFoundError virtualenv.activation.nushell since 20.8.0
See original GitHub issueIssue
expected: poetry install successfully creates virtual env
observed:
- fails with today’s new release 20.8.0
- works if I run
pip3 install 'virtualenv==20.7.2' --force-reinstall
first
Environment
Provide at least:
- OS: alpine linux 3.12
Output of the virtual environment creation
(running in docker using alpine 3.12)
RUN poetry install --no-root --no-dev
Creating virtualenv in ...
ModuleNotFoundError
No module named 'virtualenv.activation.nushell'
at <frozen importlib._bootstrap>:984 in _find_and_load_unlocked
I may be mistaken (not really a python expert), but I believe this commit/line is the culprit that broke things:
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Exception: `No module named 'virtualenv.activation.nushell ...
If an exception occurs when executing a command, I executed it again in debug mode ( -vvv option). OS version and name: python:3.9...
Read more >No module named nushell? - venv - Raspberry Pi Forums
Trying to create a venv on a Pi Zero 2 pip install virtualenv==20.4.7 pi@raspberrypi:~ $ virtualenv flaskenv ... How do I install nushell?...
Read more >ModuleNotFoundError virtualenv.activation.nushell since 20.8.0
Issue. expected: poetry install successfully creates virtual env. observed: fails with today's new release 20.8.0; works if I run pip3 install ...
Read more >Release History — virtualenv 20.17.2.dev2+g6845f6f ...
Update operator used in Nushell activation script to be compatible with ... Drop python 3.4 support as it has been over 2 years...
Read more >virtualenv - bytemeta
ModuleNotFoundError virtualenv.activation.nushell since 20.8.0 ... Make software development more efficient, Also welcome to join our telegram.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I actually don’t remember why I added that. I have now removed it and it didn’t change the behavior. Thank you for the tip.
I think I have found the problem, though - @gaborbernat was right - my container was still using poetry 1.1.7 instead of 1.1.8. With poetry 1.1.8, it works without the virtualenv downgrade.
Sorry about the confusion and thank you all for your help. Closing this.
SOLUTION TL/DR: ensure you’re on the latest poetry version!
This seems like a failed installation on debian 👍