open-feature / open-feature/python-sdk
Spec v0.9.0 compliance
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 111
- Forks
- 44
- Avg merge
- 2h 37m
- Merged PRs (30d)
- 14
Description
Tracks spec v0.9.0 compliance.
-
#615 Domain in provider init
-
#584 Isolated API instances
-
#511 Multi-provider (optional)
-
Bump test-harness/spec submodule to v0.9.0
-
Provider lifecycle event ownership (race-condition fix): add opt-in marker so providers emit their own
PROVIDER_READY/PROVIDER_ERROR; SDK derives status from the provider event stream and keeps + deprecates the legacy synthetic path; update first-party providers (spec 5.3.5, provider status 2.8, Appendix E)
Contributor guide
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 reviewing linked issues #615, #584, and #511 alongside the v0.9.0 specification sections listed in the issue. Inspect the test-harness/spec submodule and the provider event requirements first; done means every checklist item is addressed, including the lifecycle ownership change and updated first-party providers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100