Thanks for this detailed PEP and analysis, and for the interesting discussion in your separate thread. I’m glad to see this work that we chatted about all that time before has coalesced into a PEP.
FYI: For those with write access to the PEPs repo, PEP number assignments are self-serve. Just grab the next available one and manage any push race conditions accordingly. Question: > On Jan 11, 2021, at 09:21, Larry Hastings <la...@hastings.org> wrote: > > from __future__ import co_annotations > ------------------------------------- > > In the prototype, the semantics presented in this PEP are gated with: > > from __future__ import co_annotations Given that PEP 563 is now the default in unreleased Python 3.10, does it make sense to introduce yet another __future__ import? What would happen if you just piggybacked your idea onto that change? -Barry
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/FPXDS2D5RSSPDWWMIXJWNWUDAUI4QN3K/ Code of Conduct: http://python.org/psf/codeofconduct/
