Hi,
There are two key issues I have when developing python libraries and testing them on RhinoCode. I am using vscode and pip to install my local package to rhinocode python directory, since I am always working within a conda environment.
Following are key problems:
- RESTART RHINO - everytime I add new code, methods or classes in vscode I need to reload rhino. First time you pip install your package like this:
C:/Users/my_user_name/.rhinocode/py39-rh8/python.exe -m pip install -e .
But still rhino needs to be restarted every time you change code in Visual Studio Code. - CONDA - rhinocode uses its own environment so everything must be installed through PIP, this leads to two sub-problems:
2.1. I always need to switch between my conda environment and rhino editor since is impossible to work on conda.
2.2. The PIP only solution prevents to install conda packages specially c++ ones e.g. boost, cgal and others, let alone local packages that pip builds on c++ conda libraries.
I am wondering why the decision was made to have a stadalone python editor instead of more flexible conda environments that you switch simple everytime you work on different project? I think I heard this questions from multiple users.
I get that for fully polished libraries it is a great editor, but for development it is really slowing the work.
1 post - 1 participant