Closed noisy closed 5 years ago
As far as I understand, the proposed changes to the build system cause that every PR is built as a package which is then pushed to pypi repository.
The idea was to push this to test.pypi
https://github.com/tokenika/eosfactory/pull/85/files#diff-354f30a63fb0907d4ad57269548329e3R10
Also, this could be restricted by travis settings, to execute this only when code is merged to dev
PYPI distributable EOSFactory is developed in the branch 'pypi-ready', now.
Thanks to this pull requests, it possible to upload eosfactory package to https://pypi.org/.
Thanks to that instalation of eosfactory is simple as:
pip install eosfactory
Certain directories and files needed to be moved to
eosfactory/
directory, otherwise it was impossible to add to egg package non-python files, even with manifest.Settings of travis has been updated, so now Travis to be able to run tests first install eosfactory package, which during tests was build and uploaded to Test PyPi: https://test.pypi.org/project/eosfactory/#history (with version of Travis build).
Important: Travis will not build automatically release packages, and it is not advised to configure it in such a way (although it is possible). It is very important to know, that after package with version 1.2 will be uploaded, and manually deleted because of any reason... it it impossible to upload new build with the same number. In such cases, it is advisable to increase version number, for example to 1.2.1.
How to build and upload package to https://pypi.org/manage/project/eosfactory/releases/
python3 setup.py sdist bdist_wheel
to build packagetwine upload dist/*
to upload package 4.1.. You can upload to test pypi, by `twine upload --repository-url https://test.pypi.org/legacy/ dist/*https://pypi.org/manage/project/eosfactory/releases/
Example of ~/.pypirc