RosettaCommons / RosettaCommons/atomworks
Adopt Python 3.12 override decorator after dropping 3.11
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 446
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
Context: https://github.com/RosettaCommons/atomworks/pull/22#discussion_r2342477966
Request: Once Python 3.11 support is dropped, add the @override decorator (PEP 698) where applicable across the codebase.
Scope ideas:
- Add decorator to overriding methods in public APIs.
- Ensure type-checkers (mypy/pyright) run clean.
- Note the minimum Python version change in docs and changelog.
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 inventorying overriding methods across the codebase and identify the public APIs where the Python 3.12 @override decorator applies. Run mypy and pyright to confirm type-checkers remain clean, then update the documentation and changelog to record the minimum Python version change. Done means applicable overrides are annotated and both checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100