Is there a way to enable the installation of the python api from the cmake source file?
I would prefer something that produces a python3/dist-packages directory that I can simply add to the $PYTHONPATH rather than the setup.py install.
Many thanks
Is there a way to enable the installation of the python api from the cmake source file?
I would prefer something that produces a python3/dist-packages directory that I can simply add to the $PYTHONPATH rather than the setup.py install.
Many thanks
I tend to use the editable install as this allowing you to make source code changes and then import the package with the updated changes. It still males use of the setup.py but it makes a link instead of copying all the files to the python install folder.
python -m pip install-e .
This however does not work unless you are in a venv. I would prefer to be able to use the rest of the packages I have on my system. Is there no way to do that?
I have been using the following
python -m pip install -e . --prefix=
but it hasnt been copying the openmc folder containing the python bindings, it seems, found in the main openmc folder, in to the generated dist-packages directory. I am not sure what causes this but it would be nice if an option could be added to simplify the process in the CMakeLists file rather than using a whole new build system.
I manually copied that folder and Jupyter Lab finds the module, but it restarts the kernel when a calculation is running and the whole thing restarts. Any tips for this issue?
Hi,
According to the log this has something to do with pmix. Does anyone know what might be the cause? I installed mpi4py with my openmpi installation and i have billed petsc with it and it works. I am not sure what else may be causing this.
-_- it was calling a system mpi and mpi4py lib rather than locally built. I wish there was an easier way to control these variables in python builds too. At least in c++ you can force rpaths.