Pythonocc-nodes-for-Ryven
Pythonocc-nodes-for-Ryven copied to clipboard
Ryven | Load Example | demo_example.json can't find PythonOCC
Click on "AUTO IMPORT" and it finds std but can't find PythonOCC
yes, it doesn't know where the nodes package is, because when the creator of the project used it on his machine, it was under a different path. you need to locate it manually: click on ADD
, navigate to your clone of this repo and select Pythonocc-nodes-for-Ryven/PythonOCC/nodes.py
. If you then save the project on your machine it will update the paths in the project file and you don't have to locate it again next time
I don't understand "clone of this repo"?
Wasn't it installed by the command "conda install -c conda-forge pythonocc-core"?
pythonocc-core is a prerequisite (or dependency), along with pythonocc-utils, anaconda, and ryven. if you want to use this project (Pythonocc-nodes-for-Ryven), you have to download it too, i.e. clone the repository via git clone https://github.com/Tanneguydv/Pythonocc-nodes-for-Ryven
I guess the thing which I'm missing here is the difference between just using python at the terminal, using anaconda, and the difference in accessing one or the other.
Is there a set of step-by-step instructions, which assume nothing, for installing on Linux?
What happened to the pythonocc.org website?
yeah, I don't know if there are more detailed instructions for PythonOCC, but you will find plenty of resources online which take you through the process of installing the Anaconda platform, setting up a new conda environment, and then installing packages in this environment, which is what you need.
and to prevent confusion: you can have (and usually do have) various Python installations on your system, and Anaconda will also bring its own Python installation. So, yes when using PythonOCC you are using Python, but you use it inside an Anaconda environment
Once everything installed you can create a .bat
file with this text :
call activate pyoccryv3env
ryven
pause
where pyoccryv3env is the virtual environment you have setup to run Ryven with PythonOCC
Then create a shortcut of this .bat
file to havae easy access to Ryven.
Personnaly I use Miniconda instead of Anaconda, and I use Pycharm to easily access virtual environnement and code in a python friendly IDE
You can find all ressources on PythonOCC from this link :https://github.com/tpaviot/pythonocc-core
The problem seems to be that I can't get a working nodes.py loaded.
I've downloaded and unzipped: https://github.com/Tanneguydv/Pythonocc-nodes-for-Ryven/archive/refs/heads/main.zip
and if I point it at:
it won't press
and if I point it at:
get:
and if both:
(base) C:\Users\willa>ryven
importing packages...
Traceback (most recent call last):
File "C:\Users\willa\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "C:\Users\willa\AppData\Local\Programs\Python\Python310\lib\runpy.py", line 86, in run_code
exec(code, run_globals)
File "C:\Users\willa\AppData\Local\Programs\Python\Python310\Scripts\ryven.exe_main.py", line 7, in
I think that your installation of Ryven does not belong to the virtual environment created with OCC installation, that's why the module OCC can't be found while launching Ryven I guess.
At the installation of OCC you created a virtual env (named such as pyoccenv
), you have to install Ryven in this same virtual environment (conda activate pyoccenv
then pip install ryven
)
@Tanneguydv what is the difference between the two nodes files? there should only be one in PythonOCC/
There's only one node file, no?
repo/nodes.py
https://github.com/Tanneguydv/Pythonocc-nodes-for-Ryven/blob/main/nodes.py
repo/PythonOCC/nodes.py
https://github.com/Tanneguydv/Pythonocc-nodes-for-Ryven/blob/main/PythonOCC/nodes.py
which caused some confusion above, there should only be 1, the files are identical
#14
My Bad, I'll fix this
removed, I closed your pull request, thank you!
Okay, the command:
source activate pyoccenv
from: https://github.com/tpaviot/pythonocc-core doesn't seem to work --- instead used:
conda activate pyoccenv
Also, python can't equal 3.10