Open-EO / Open-EO/openeo-python-driver
openeo-processes-python dependency: eliminate, fork, vendor in, ...?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
in 65a873548850c2ed255c42a092a593cf8e8e7870 I added dependency on https://github.com/Open-EO/openeo-processes-python to easily implement some non-cube processes, like:
https://github.com/Open-EO/openeo-python-driver/blob/6abf10b5ff28a275ae1b8e6c2e5598130b419cc3/openeo_driver/ProcessGraphDeserializer.py#L114-L125
openeo-processes-python is however being sunset and not maintained anymore, so we need some way to move forward with this dependency:
- maintain minimal fork with custom releases when necessary
- vendor-in the project as a whole
- just copy over the necessary parts
Also note that we depend on a very old release, 0.0.4, of that library (also see https://github.com/Open-EO/openeo-processes-python/issues/15) , while the latest master has quite diverged from that
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the dependency usage in ProcessGraphDeserializer.py around lines 114-125 and the project's reliance on openeo-processes-python 0.0.4; also review the upstream issue 15. Compare the fork, vendoring, and copying options, then select and implement a migration path that preserves the affected non-cube processes without relying on the sunset dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100