OpenAssetIO / OpenAssetIO/Template-OpenAssetIO-Manager-Python
Move dependencies to extras
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
What
Remove hard dependency on openassetio and openassetio-mediacreation and move to extras
Why
openassetio should always be provided by the host runtime (to ensure we don't have multiple copies loaded simultaneously). Having it as a hard dependency anywhere up the stack causes problems, as pip will try and provision it too, which usually results in a separate static build being installed in addition to whatever the host provides (unless the host is pure python).
ACs
openassetiomoved to a extras dep under theallanddepsnamesopenassetio-mediacreationmoved to an extras dep under thedepsname. [TBC]
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 by locating the package dependency configuration and inspect how the existing openassetio and openassetio-mediacreation requirements are declared. Verify that openassetio is available through the all and deps extras, and that openassetio-mediacreation is available through deps; resolve the noted uncertainty before treating the work as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100