Open-EO / Open-EO/openeo-python-driver
slim down essential openeo-python-driver dependencies
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 8
- Avg merge
- 6d 3h
- Merged PRs (30d)
- 4
Description
openeo-python-driver contains some functionality (which requires certain dependencies) that are specific to the main downstream user: the geopyspark driver.
the python driver is actually also the driver for the openeo-aggregator, which does not require some dependencies required for concrete processing (numpy, xarray, pandas, ...)
It would help simplifying the packaging/dockerizing of openeo-aggregator if these unused dependencies can be avoided
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 setup.py lines 52-75 and compare the listed dependencies with the functionality used by the openeo-aggregator versus the geopyspark driver. Determine a packaging arrangement that avoids unnecessary concrete-processing dependencies for the aggregator while retaining the dependencies required by the driver, then verify the resulting packaging or Docker setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- numpy, pandas, python
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100