[issue33124] Lazy execution of module bytecode

Josh Rosenberg added the comment: Serhiy: There is a semi-common case where global constants can be quite expensive, specifically, initializing a global full of expensive to compute/serialize data so it will be shared post-fork when doing multiprocessing on a

[issue33124] Lazy execution of module bytecode

Serhiy Storchaka added the comment: Function definitions usually are cheap, as well as global constants definitions (unless they use complex comprehensions or call heavy functions for initialization). Creating a class is an order or more slower than creating a

[issue33124] Lazy execution of module bytecode

Change by Brett Cannon : -- nosy: +brett.cannon ___ Python tracker ___ ___

[issue33124] Lazy execution of module bytecode

Change by Barry A. Warsaw : -- nosy: +barry ___ Python tracker ___ ___ Python-bugs-list

[issue33124] Lazy execution of module bytecode

Change by Neil Schemenauer : -- keywords: +patch pull_requests: +5941 ___ Python tracker ___

[issue33124] Lazy execution of module bytecode

New submission from Neil Schemenauer : This is an experimental patch that implements lazy execution of top-level definitions in modules (functions, classes, imports, global constants). See Tools/lazy_compile/README.txt for details. -- components: Interpreter