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 pfalcon
Recipients pablogsal, pfalcon, ppperry, terry.reedy, vstinner
Date 2020-01-16.23:34:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Namespace performances are really critical for overall Python performances.

Yeah, that's why I'd like for myself and other people to make it easy to explore the behavior of namespace lookups, to see how to optimize them.

> You're free to fork Python and modify the C code to implement your use case, to study Python internals.

Thanks, already done. I'm now looking for a way to share those studies with other people, who won't patch and compile CPython. So, no worries, I've already lost, I need that fix yesterday, in actual versions of CPython deployed around the world. The rest if just idea that bugs which aren't fixed, persist; and the very interesting case of decision making by CPython core developers.
Date User Action Args
2020-01-16 23:34:27pfalconsetrecipients: + pfalcon, terry.reedy, vstinner, ppperry, pablogsal
2020-01-16 23:34:27pfalconsetmessageid: <>
2020-01-16 23:34:27pfalconlinkissue32615 messages
2020-01-16 23:34:27pfalconcreate