Can't add virtualenv environment in PyCharm 2019.1 with Anaconda3 under Windows 10
I'm setting up my new PC and I've just installed Anaconda3 and PyCharm 2019.1. When I'm trying to add virtualenv environment to "Settings to New Projects", it just can't work.
At first it kept reminding me that "FileNotFoundError: [Errno 2] No such file or directory: 'C:\Users\jackson\AppData\Local\Continuum\anaconda3\lib\venv\scripts\nt\pythonw.exe'"
And I checked into that path, there indeed wasn't a "pythonw.exe". So I copied one from Anaconda directory into this "nt" folder, and tried to create this environment again. Then the error message becomes "Permission denied" when executing command "..\PyCharm 2019.1\helpers\packaging_tools.py list".
I tried running PyCharm with Administrator permission but it still can't work. Please help me, thanks.
Please sign in to leave a comment.
Just solved the problem.
Uninstalled Anaconda3 (Version 19.1) and reinstalled Anaconda3 18.12.
Seems that there're some bugs with the newest Anaconda3.
I am having the same problem with PyCharm. I don't think this is a bug in Anaconda because Visual Studio 2019 works perfectly with the same Anaconda installation.
PyCharm 2019.1.3 (Community)
Visual Studio 2019 (Community)
I believe it's related to the following issue: https://youtrack.jetbrains.com/issue/PY-35053
Anyway, why would you create a virtualenv with Anaconda interpreter? Anaconda have it's own conda environments, why not use them?
I had the exact same error. Solution was, as @brandon describes, uninstall anaconda 19 and install anaconda 18
I had also the exact same problem. My solution with fresh install (Anaconda3 2019.07, PyCharm Community Edition 2019.2.1): First go to Anaconda command prompt and conda update conda, conda update python. Then install OpenSLL for Windows(*). Create project and select first interpreter as System wide Python. And finally create virtual environment for my project, and especially install new packages to it from PyCharm interface.
(*) Sorry, I don't find the thread anymore that was discussing about the "OpenSSL step". Anyway this is now confirmed with two computers (running latest updates with Windows 10)