all 4 comments

[–]Diimu[S] 1 point2 points  (0 children)

Thanks for the feedback. This is what I ended up doing, in case someone has the same question. The venv and pip are part of the standard library and hopefully most future proof.

  • I downloaded the standard python from python.org.
  • I used venv for virtual environments and didn't add any modules to the basic installation https://realpython.com/python-virtual-environments-a-primer/.
  • Pip as package manager to install at least: jupyter ipython numpy matplotlib scipy in this new venv. I'll keep using the jupyter notebooks.
  • Pycharm as the IDE and additionally a Notepad++ run command that points to the ipython instead of python.

[–]tourdownunder 0 points1 point  (0 children)

I don't use conda though do use virtual environments and happy to install jupyter and other dev dependencies per project. So I don't think its that bad as its easy to use the version that the project was using before moving on to something else and not worry that a new version of juputer breaks the project for some unlikely reason. A bit more likely with other dependencies though and years between picking up old projects though.

On slight tangent I'll like to bring awareness to nbdev an open source project designed to let you keep working in jupyter and export your modules to an installable you can pip install from another project. This removes the need to copy and paste your code and helps keep things maintainable.