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 gvanrossum
Recipients BTaskaya, Mark.Shannon, brandtbucher, brett.cannon, eric.snow, gvanrossum, larry, lemburg, nascheme, ronaldoussoren
Date 2021-08-28.00:37:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1630111020.26.0.335168925986.issue45020@roundup.psfhosted.org>
In-reply-to
Content
Adding Larry in case he remembers more color. (Larry: the key question here is whether some version of this (like the one I've been working on, or a simpler one that Eric has prepared) is viable, given that any time someone works on one of the frozen or deep-frozen stdlib modules, they will have to run make (with the default target) to rebuild the Python binary with the deep-frozen files.

(Honestly if I were working on any of those modules, I'd just comment out some lines from Eric's freeze_modules.py script and do one rebuild until I was totally satisfied with my work. Either way it's a suboptimal experience for people contributing to those modules. But we stand to gain a ~20% startup time improvement.)

PS. The top comment links to Eric's work.
History
Date User Action Args
2021-08-28 00:37:00gvanrossumsetrecipients: + gvanrossum, lemburg, brett.cannon, nascheme, ronaldoussoren, larry, Mark.Shannon, eric.snow, brandtbucher, BTaskaya
2021-08-28 00:37:00gvanrossumsetmessageid: <1630111020.26.0.335168925986.issue45020@roundup.psfhosted.org>
2021-08-28 00:37:00gvanrossumlinkissue45020 messages
2021-08-28 00:37:00gvanrossumcreate