FWIW, I'm in agreement. My "forward class" proposal(s) were me
trying to shine a light to find a way forward; I'm in no way
adamant that we go that direction. If we can make 649 palatable
without introducing forward declarations for classes, that's
great! If in the future we discover more edge cases that Carl's
approach doesn't easily solve, we could always revisit it later.
For now it goes in the freezer of "ideas we aren't moving forward
with".
/arry
FWIW, Carl presented a talk about his proposed way forward using PEP 649 with some small enhancements to handle cases like dataclasses (*), and it was well received by those present. I personally hope that this means the end of the "forward class declarations" proposals (no matter how wonderful), but the final word is up to the SC.
(*) Mostly fixing the edge cases of the "eval __code__ with tweaked globals" hack that Carl came up with previously, see https://github.com/larryhastings/co_annotations/issues/2#issuecomment-1092432875.
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@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/EBDKGKPMOHM674PMUXCVZDRUD5NTIKZB/ Code of Conduct: http://python.org/psf/codeofconduct/