Tiny utility to launch a script in a separate process, possibly using another python executable/environment. The script may be accessed from the main process through a proxy. This project relies on the default multiprocessing module, therefore the child environment does not require any particular package to be present (not even this package).
BSD-3-CLAUSE License
Spawn python code in a separate python interpreter and communicate with it easily.
This is the readme for developers. The documentation for users is available here: https://smarie.github.io/python-spawny/
Contributions are welcome ! Simply fork this project on github, commit your contributions, and create pull requests.
Here is a non-exhaustive list of interesting open topics: https://github.com/smarie/python-spawny/issues
This project uses pytest
.
pytest -v spawny/tests/
You may need to install requirements for setup beforehand, using
pip install -r ci_tools/requirements-test.txt
This project uses setuptools_scm
to synchronise the version number. Therefore the following command should be used for development snapshots as well as official releases:
python setup.py egg_info bdist_wheel rotate -m.whl -k3
You may need to install requirements for setup beforehand, using
pip install -r ci_tools/requirements-setup.txt
This project uses mkdocs
to generate its documentation page. Therefore building a local copy of the doc page may be done using:
mkdocs build -f docs/mkdocs.yml
You may need to install requirements for doc beforehand, using
pip install -r ci_tools/requirements-doc.txt
The following commands generate the html test report and the associated badge.
pytest --junitxml=junit.xml -v spawny/tests/
ant -f ci_tools/generate-junit-html.xml
python ci_tools/generate-junit-badge.py
This project is now automatically deployed to PyPI when a tag is created. Anyway, for manual deployment we can use:
twine upload dist/* -r pypitest
twine upload dist/*