Skip to content
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

pypi release for 0.4 #68

Closed
m-mohr opened this issue Jul 18, 2019 · 5 comments
Closed

pypi release for 0.4 #68

m-mohr opened this issue Jul 18, 2019 · 5 comments

Comments

@m-mohr
Copy link
Member

m-mohr commented Jul 18, 2019

Could we get a pypi release for 0.4 once it is ready, please? This would allow us to use this library as a dependency for other projects, e.g. the backend-result-validator. See Open-EO/openeo-result-validation-engine#43

@soxofaan
Copy link
Member

Agree.

A couple of notes

  • the python client version is currently 0.0.5. Is there plan/intention to keep the openEO API versions in sync in some way with client versions (e.g. client version x.y.z is supposed to support openEO API up to at least x.y.z)? I'm not sure this is necessary or useful. On the contrary, this coupling could make things more complicated.
  • is there already a PyPI account for uploading/managing openEO related python packages on PyPI?
  • @jdries is on holiday till mid August since today, I am also two weeks away starting tomorrow, so it is not likely that this issue will be addressed quickly from the VITO side

@m-mohr
Copy link
Member Author

m-mohr commented Jul 19, 2019

Is there plan/intention to keep the openEO API versions in sync in some way with client versions

No, not at all. For some libraries (Web Editor, JS, R) this is the case at the moment for minor versions (e.g. JS client 0.4.0 supported API 0.4.0/1/2), but that's more a somewhat useful coincidence than a planned behaviour. So feel free to release it with whatever version you'd like, but according to the guidelines for the project, SemVer should be followed. See point 9.

  • is there already a PyPI account for uploading/managing openEO related python packages on PyPI?

I don't think there is an account yet as there's no package yet.

  • so it is not likely that this issue will be addressed quickly from the VITO side

Not a big deal, I think. We should release only once it's "ready" and I think the Python client needs some more work beforehand?

@soxofaan
Copy link
Member

soxofaan commented Aug 5, 2019

We should release only once it's "ready" and I think the Python client needs some more work beforehand?

Indeed, some more work is needed before it can be considered "ready".
On the other hand, we can already set up the necessary things: the client's version at the moment is only '0.0.5' which should indicate that it is not ready yet for broad consumption.

@m-mohr
Copy link
Member Author

m-mohr commented Aug 5, 2019

You could also release something like x.x.x-beta.1, which is what I do for the JS client, Web Editor etc.

@jdries
Copy link
Collaborator

jdries commented Nov 30, 2019

Closing: multiple pypi releases have been published already, and we regularly create new releases.

@jdries jdries closed this as completed Nov 30, 2019
soxofaan added a commit that referenced this issue Sep 18, 2023
…tency

The "round up" end_date feature as originally proposed
turned out to conflict too much with existing behavior and openEO spec.

Still, the idea can still be provided through single string `extent`: "2022" -> ("2022-01-01", "2023-01-01")
soxofaan added a commit that referenced this issue Sep 18, 2023
soxofaan added a commit that referenced this issue Sep 18, 2023
soxofaan added a commit that referenced this issue Sep 20, 2023
…tency

The "round up" end_date feature as originally proposed
turned out to conflict too much with existing behavior and openEO spec.

Still, the idea can still be provided through single string `extent`: "2022" -> ("2022-01-01", "2023-01-01")
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants