Add regret.policies.Manual
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 15
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
This deprecation "policy" is the degenerate case -- deprecated objects are removed at an arbitrary (or externally specified, or un-specified) manually specified point in time.
Under this policy no errors can be shown by e.g. #14 / #1, but we likely should show a warning if those helpers are used that there's no way to check them against this policy.
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
Review the existing deprecation-policy implementation and the helpers referenced by #14 and #1. Determine how a manually specified removal point fits the policy interface and how those helpers should behave when the policy cannot be checked. Done means regret.policies.Manual is available and the helper behavior matches the issue’s warning requirement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100