2017-10-02 16:48 GMT+02:00 Christian Heimes <christian at python.org>: > That approach could work, but I think that it is the wrong approach. I'd > rather keep Python optimized for long-running processes and introduce a > new mode / option to optimize for short-running scripts. "Filling caches on demand" is an old pattern. I don't think that we are doing anything new here. If we add an opt-in option, I would prefer to have an option to explicitly "fill caches", rather than the opposite. I know another example of "lazy cache": base64.b85encode() fills a cache at the first call. Victor
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4