-
Notifications
You must be signed in to change notification settings - Fork 42
Provide openeo package on conda-forge #176
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
Comments
We do manage most packages with conda in the EGI Notebooks service and having packages in conda would simplify the installation of OpenEO. |
Hi, I am happy to help create a conda package for @soxofaan could you please have a look and provide feedback? Would you like to be included as a conda package maintaner? Best regards, |
Hi @sebastian-luna-valero , thanks this is very helpfull, as we don't have experience with this ourselves! |
Hi Sebastian, |
Hi Jeroen, I am happy to wait until Stefaan can have a look. It is also possible to just build and release the conda package for Linux, and forget about OSX and Windows for now. Best regards, |
Hi, FYI: I will be on leave the last two weeks of August, so I will be available to help with the conda package either next week or after 31st of August. Best regards, |
Hi @sebastian-luna-valero thanks for bootstrapping this! I already had a quick look at conda-forge/staged-recipes#15717 I also did a minor tweak that should hopefully fix the failing tests on osx |
Many thanks @soxofaan I am now updating the recipe. Let's continue the discussion over there, please. |
Hi @soxofaan Do you need more time before we continue working on conda-forge/staged-recipes#15717? Or can I add Best regards, |
hi @sebastian-luna-valero sorry for the delay. |
Hi @soxofaan No worries. I added my comments to the |
Thanks, following up discussion on conda-forge/staged-recipes#15717 |
Ok it seems openeo is now available for conda (forge): https://anaconda.org/conda-forge/openeo I just tried to install it in a fresh conda env (with python 3.9) and it gave this package plan:
This looks quite a bit more than what a standard pip install drags in:
@sebastian-luna-valero could it be that the dependency listing in the conda recipy needs a bit more fine-tuning or pruning? |
Hi @soxofaan I see. However, what we added to the conda recipe: Is equal to what we have in: So the differences are due to the dependency resolution made by What would you modify in the conda recipe then? |
@sebastian-luna-valero Another related question:
Do you know approaches or tools to keep these things in sync? Yesterday for example, I added a new test dependency, which eventually should be added to the conda recipy too. Thanks by the way for pushing this ticket, and apologies it took so long to get all the kinks out. |
Sorry, I don't know.
No worries, and thanks for your support! |
👍 I think we can close this ticket for now. |
@sebastian-luna-valero I just released version 0.15.0 of python client. Can you walk me through the steps required to also get that release in conda-forge? |
Hi @soxofaan conda-forge automatically opens a PR when a new version of the source code is available: conda-forge/openeo-feedstock#1 Since you are listed as a recipe maintainer you are also notified. It's now up to us to review and merge that PR. Once the PR is merged, the new conda package will be created and released via the conda-forge channel. |
We provide openeo python client library already on pypi.org, but it could be beneficial to our adoption rate and installation friendliness to also provide it through conda on conda-forge channel.
I'm not sure at the moment what has to happen to make it possible, how much additional maintenance it would require and if it is all worth the trouble. Just putting it out here to collect some feedback, if any.
The text was updated successfully, but these errors were encountered: