-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
push releases to PyPI #252
Comments
documentation example where I had to add the extra-url: https://github.com/Open-EO/openeo-test-suite/blob/7dd98b1737a3d241974400a1e7f30778835490fa/README.md?plain=1#L66-L73 |
soxofaan
added a commit
that referenced
this issue
Jan 29, 2024
I decided to already push a release to avoid other people stealing our package name on pypi: |
soxofaan
added a commit
to Open-EO/openeo-test-suite
that referenced
this issue
Feb 5, 2024
pypi already has first release of openeo_driver Open-EO/openeo-python-driver#252
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some public projects like https://github.com/Open-EO/openeo-aggregator and https://github.com/Open-EO/openeo-test-suite depend on openeo-python-driver. The package is not available on PyPI, but only on VITO artifactory. This requires the user to link to VITO artifactory (e.g.
pip ... --extra-index-url
with appropriate URL).This is extra cruft to document in various places, and it is not always easy to get it right in some tooling contexts.
I think we should push some releases from time to time to PyPI
The text was updated successfully, but these errors were encountered: