Otherwise, please consider it for the subsequent release.

Thanks for responding, I guess I'm just as disappointed the 'fix' wasn't in the 2019.1 EAP I downloaded. I'm not familiar with the code base IntelliJ developers have to deal with but this seems like a reasonable requirement amendment (or bug fix) to consider.Īnyways, I really like P圜harm overall, it has been making our development more efficient. I expect the Python Console and Run Configurations to do the same but surprisingly that is not the case. When I have a virtual environment selected as project interpreter, the Terminal has no trouble activating it. It seems rational to expect our IDE to do the same. The basic introduction to python virtual environments instructs us to activate them. The virtual environment's activation script is not ran and that is troublesome for some members of the python community. Python extension in Visual Studio Code (a great Python IDE like P圜harm, if not the best Python IDE). I'm relieved that there are workarounds for library paths but you should still know that this isn't a fix. Now with the release of HomeAssistant 0.116. We added the library paths to our project interpreter Paths. How to upgrade Python venv to 3.8.6 If you are running Home Assistant on a Raspberry Pi with Python and manually installed it, you prob are running it in a Virtual Environment (venv) like me.

We have come up with a similar work around here.

Pycharm venv