Consider adding error-checking for deprecating already-deprecated things
Open
- Dominant language
- Python
- Stars
- 15
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Maybe
```
@regret.callable(...)
@regret.callable(...)
def foo()
...
```
should be an error. Doubt it matters much, and this will get more complicated when e.g. sub-portions of things are deprecatable (e.g. just one argument), but adding to track.
Contributor guide
Assessment
This issue has not been assessed yet.