Message249150
_warnings.c was initially created to help with startup performance. It turned out to be a tricky bit of code to get right to continue to support the Python version of the module.
But now that we live in a world where we have startup benchmarks instead of hunches and we freeze code like importlib, maybe it's time to re-evaluate whether warnings.py is such a bad thing to have as part of the startup process? I would be curious to know what the performance impact is if we made _warnings the frozen version of warnings.py instead of the C code and measured the startup performance. |
|
Date |
User |
Action |
Args |
2015-08-25 18:49:27 | brett.cannon | set | recipients:
+ brett.cannon |
2015-08-25 18:49:27 | brett.cannon | set | messageid: <1440528567.54.0.786073455364.issue24938@psf.upfronthosting.co.za> |
2015-08-25 18:49:27 | brett.cannon | link | issue24938 messages |
2015-08-25 18:49:27 | brett.cannon | create | |
|