One more feature for pyfastchem users here. It's traditional to install python packages using Python itself, rather than building with cmake first and generating a standalone shared library. The advantages to doing this include:
the typical call to python setup.py install will work
the package pyfastchem will be installed at the system level, so that it can be imported anywhere, without specifying the path to the shared library
the average Python user needs to know less C to make the install happen
With this addition, you can simply cd into the repo and type python setup.py install to install the package.
Also, if you approve of these changes and want me to handle it for you, I can also upload pyfastchem to PyPI (this is something I need for one of my projects), so it can also be installed simply with pip install pyfastchem.
Hi @daniel-kitzmann,
One more feature for pyfastchem users here. It's traditional to install python packages using Python itself, rather than building with cmake first and generating a standalone shared library. The advantages to doing this include:
python setup.py install
will workpyfastchem
will be installed at the system level, so that it can be imported anywhere, without specifying the path to the shared libraryWith this addition, you can simply
cd
into the repo and typepython setup.py install
to install the package.Also, if you approve of these changes and want me to handle it for you, I can also upload pyfastchem to PyPI (this is something I need for one of my projects), so it can also be installed simply with
pip install pyfastchem
.