pycharm-bash in the root of your project. Open your P圜harm project and create a file name. Here’s the solution I use to both of those issues: Actually, depending on your settings, the workon command may not even be found anyway. However, this environment isn’t activated by default when you launch the P圜harm terminal. The workon command sets the environment so now anything you do with Python is looking at the Python and all installed packages that are in that environment only. With VirtualEnvWrapper, you jump into your project environment by typing: However, one thing that it doesn’t tie together nicely is the use of the built-in terminal with the virtual environment you have associated with the opened project. They work well together too! P圜harm has built-in support for virtual environments and even allows you to manage and install new PIP packages directly into your project’s virtual environment. So, to recap this crazy-long post so far, P圜harm = Awesome & VirtualEnvWrapper = Awesome. I personally use the popular VirtualEnvWrapper and it’s a great solution to help manage your virtual environments. And, if you do Django, you should also be using virtual environments to help keep your python projects separated nicely. If you do Django, you should do P圜harm as well. P圜harm is an incredible Python IDE made by JetBrains, and it’s my go-to editor for all Django development.

Pycharm venv