This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author larry
Recipients The Compiler, eric.smith, gvanrossum, kj, larry, levkivskyi
Date 2021-04-16.19:45:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
It would also cause the code generated for the annotations function to balloon--the calculation of every value would have to be wrapped in a try/except, and for what I assume is an obscure use case.  I'm already getting some pushback on the code generated with PEP 649 as it is.

My goal in designing PEP 649 was to take stock semantics and time-shift the evaluation of the annotations, adding as little opinion as possible.  I think catching NameErrors is too opinionated, much less catching every plausible error.

Still, the approach is mentioned in PEP 649.  I assume the Steering Committee rules is aware this option exists.  If they rule in favor of adding PEP 649, but stipulate that this feature is necessary, I will of course implement it.
Date User Action Args
2021-04-16 19:45:15larrysetrecipients: + larry, gvanrossum, eric.smith, The Compiler, levkivskyi, kj
2021-04-16 19:45:15larrysetmessageid: <>
2021-04-16 19:45:15larrylinkissue43463 messages
2021-04-16 19:45:15larrycreate