@kumaraditya303 this was my exact question. Because, current version of PEP states:

This is why starting with Python 3.9, the following collections become generic using class_getitem() to parameterize contained types:

I have several issues with that:

• Python3.9 won't support (without __future__ import) generic property[] as far as I understand (I might be wrong here)
• property is not a "collection" (as many other types there)

CC @ambv as PEP's author 🙂

LGTM but the PEP should be changed first to account for this change.

@kumaraditya303 I am not sure how did you end up with this idea. PEP's are historical documents, and they don't get updated as the language grows. There were multiple occurrences of generic support for classes that the PEP initially did not target (the most recent one I recall is graphlib.TopologicalSorter).

@sobolevn You can simply wait for a few core developers to respond, or just post this on the python-dev (since this is more of a change in the builtins).

I am not sure how did you end up with this idea. PEP's are historical documents, and they don't get updated as the language grows. There were multiple occurrences of generic support for classes that the PEP initially did not target (the most recent one I recall is graphlib.TopologicalSorter).

This changes property which is in the builtins which is very widely used and it not in other module so it should be mentioned in the PEP under 3.11 changes for maximum visibility about this change.

This changes property which is in the builtins which is very widely used and it not in other module so it should be mentioned in the PEP under 3.11 changes for maximum visibility about this change.

We generally do not change old PEPs, especially when they are in the Final state. A new discussion can (or should [depending on the complexity of this feature]) be brought up on python-dev, though for a case like this I'd personally suggest just waiting the final resolution in python/typing#985 and also the responses of other developers interested in typing before making an action towards python-dev since it might evolve a bit (which I personally do not expect).