Uh oh!
There was an error while loading. Please reload this page.
CONTRIBUTING: Add @deprecated, other updates - #11005
Conversation
Fixespython#11004. I started out just documenting conventions with `@deprecated`, but found some other things in need of updates. - PEP 585 and 612 are now fully supported - Add several other PEPs that we fully support - Use updated links to PEPs - Split off a few sections from the long "Conventions" section - PEP 688 was accepted
| A few guidelines for how to use it: | ||
| * In the standard library, apply the decorator only in Python versions |
There was a problem hiding this comment.
Commented in the issue, but I think it would be nice to be more aggressive in cases where an appropriate replacement already exists. (I couldn't quite tell if there was consensus in the issue, if there was then that's fine!)
There was a problem hiding this comment.
I agree now, reworded the section to say we should apply it to versions where a good replacement exists.
srittau
left a comment
There was a problem hiding this comment.
The header "The following features are partially supported:" could be removed, since the list was removed.
JelleZijlstra
commented
Nov 18, 2023
@srittau I'm actually going to move PEP 702 into that section as there are some bugs that mean we can't use it in certain contexts yet. |
Uh oh!
There was an error while loading. Please reload this page.
AlexWaygood
commented
Nov 18, 2023
I'm guessing pytype just doesn't like have two decorators stacked anywhere in a stub. I'm guessing it also crashes if you try to deprecate an abstractmethod |
JelleZijlstra
commented
Nov 18, 2023
Probably, I guess it's not worth listing exactly which decorators are problematic. |
Fixes#11002.
I started out just documenting conventions with
@deprecated, butfound some other things in need of updates.