[issue24938] Measure if _warnings.c is still worth having

2015-09-06 Thread Brett Cannon
Brett Cannon added the comment: After thinking about it and with _warnings.c not exactly changing very much I think I'm going to call YAGNI on ripping out _warnings.c. -- resolution: -> works for me status: open -> closed ___ Python tracker

[issue24938] Measure if _warnings.c is still worth having

2015-08-26 Thread Brett Cannon
Brett Cannon added the comment: Here are the benchmark results of freezing warnings.py as _frozen_warnings (very quick hack which doesn't use _frozen_warnings is attached). Basically -S slows down by about 3% and normal startup has no measurable impact. Not sure if that's worth it to simplify

[issue24938] Measure if _warnings.c is still worth having

2015-08-25 Thread Brett Cannon
Brett Cannon added the comment: I should also mention the other motivating factor was providing C access to the warnings system, but once again importlib blazed that trail already by providing a C API which simply uses the Python code. -- ___

[issue24938] Measure if _warnings.c is still worth having

2015-08-25 Thread Brett Cannon
New submission from Brett Cannon: _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