open-feature / open-feature/python-sdk
Python V1 Release
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 111
- Forks
- 44
- Avg merge
- 2h 37m
- Merged PRs (30d)
- 14
Description
I'd like us to consider releasing a v1.0 of this SDK. After a cursory inspection, I think we've implemented the spec up the most recent release. In addition to that, the usage as reported by PyPI is comparable to our other v1.0+ SDKs.
That leaves us with a few tasks:
- Audit the SDK to ensure we are spec compliant
- Fix any outstanding bugs that would significantly blemish v1.0
- Remove any deprecations we don't want to carry forward into v1.0
- Make any last minute breaking changes to function/type names etc, for ergonomic improvements
Please weigh in with your vote of confidence (or not). Also feel free to mention or create any issues that you believe are blockers.
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 auditing the Python SDK against the current OpenFeature specification, then review outstanding bugs, deprecations, and public function or type names. The issue names no files or tests, so first map each checklist item to the relevant code and existing issues. Done means blockers are resolved or explicitly accepted and the project has a clear v1.0 release decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100