Hi, have you tried creating a new WSL interpreter? You can do that by clicking on three dots button in the existing interpreter section and select WSL interpreter.
PyCharm 2019.3.1 (Professional Edition) Build #PY-193.5662.61, built on December 18, 2019 Licensed to Antonio Garcia Subscription is active until July 8, 2020 Runtime version: 11.0.5+10-b520.17 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o Windows 10 10.0 GC: ParNew, ConcurrentMarkSweep Memory: 972M Cores: 8 Registry: Non-Bundled Plugins: IdeaVIM
There is no error. I installed Pycharm on a Windows 10 machine that has WSL installed. When I tried to create a new project, I get stuck on the step as shown in the first screenshot. Basically, I only have WSL and python installed there. The Windows environment does not have Python installed so I think that's where the bug would be.
Can you try to setup a new environment on Windows 10 with a WSL installation but don't install python on your Windows Environment? I'm sure you will be able to reproduce the problem.
Dgarciacampos, the workaround in https://youtrack.jetbrains.com/issue/PY-39628 not work for me, the only way is create project by shell and open with pycharm. but for pycharm this is a bug. Now Im using 2019.2
Yes, I have tried it myself and can confirm it's working. If it still doesn't work for you, please provide steps to reproduce the issue and screenshot of the error.
Guys, this is super weak for a professionally supported product. We're likely gonna switch a whole org over to VS Code, which offers perfect WSL integration.
I tried entering a path but in the remote project location and it doesn't work. As of now, I can't use pycharm at all with wsl.
Hi, have you tried creating a new WSL interpreter? You can do that by clicking on three dots button in the existing interpreter section and select WSL interpreter.
Hi,
Yes I have created at least 4 of them. I always get the same error.
Here is the version:
PyCharm 2019.3.1 (Professional Edition)
Build #PY-193.5662.61, built on December 18, 2019
Licensed to Antonio Garcia
Subscription is active until July 8, 2020
Runtime version: 11.0.5+10-b520.17 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
GC: ParNew, ConcurrentMarkSweep
Memory: 972M
Cores: 8
Registry:
Non-Bundled Plugins: IdeaVIM
Is anyone going to help out with this problem?
Can you please show the screenshots of each step you take to create a new WSL intepreter, including the resulting error?
There is no error. I installed Pycharm on a Windows 10 machine that has WSL installed. When I tried to create a new project, I get stuck on the step as shown in the first screenshot. Basically, I only have WSL and python installed there. The Windows environment does not have Python installed so I think that's where the bug would be.
Can you try to setup a new environment on Windows 10 with a WSL installation but don't install python on your Windows Environment? I'm sure you will be able to reproduce the problem.
Thank you,
David
before this update it's work well. Now I got the same error, and can only start project in wsl shell, waiting for help.
Yes, thank you, I could reproduce the issue easily and apparently there's a ticket for this: https://youtrack.jetbrains.com/issue/PY-39628
Unfortunately at the moment we can't create a new project with WSL interpreter. Please follow the workaround from that ticket.
Andrey, did you try the workaround yourself?
I think I tried that before and it didn't work. please confirm that you have tried it and that it worked for you.
BR David
Dgarciacampos, the workaround in https://youtrack.jetbrains.com/issue/PY-39628 not work for me, the only way is create project by shell and open with pycharm. but for pycharm this is a bug. Now Im using 2019.2
@ Dgarciacampos
Yes, I have tried it myself and can confirm it's working. If it still doesn't work for you, please provide steps to reproduce the issue and screenshot of the error.
Guys, this is super weak for a professionally supported product. We're likely gonna switch a whole org over to VS Code, which offers perfect WSL integration.
@...
The issue was fixed in 2020.1, could you try updating and let me know if the issue is still reproduced for you?