[Python-Dev] Design Philosophy: Performance vs Robustness/Maintainability
Victor Stinner
victor.stinner at gmail.com
Tue Jul 18 12:12:09 EDT 2017
More information about the Python-Dev mailing list
Tue Jul 18 12:12:09 EDT 2017
- Previous message (by thread): [Python-Dev] Design Philosophy: Performance vs Robustness/Maintainability
- Next message (by thread): [Python-Dev] Design Philosophy: Performance vs Robustness/Maintainability
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Python-Dev] Design Philosophy: Performance vs Robustness/Maintainability 2017-07-18 18:08 GMT+02:00 Ethan Furman <ethan at stoneleaf.us>: > Nick Coughlan: > ------------- >> >> As another example of this: while trading the global import lock for >> per-module locks eliminated most of the old import deadlocks, (...) Minor remark: the email subject is inaccurate, this change is not related to performance. I would more say that it's about correctness. Python 3 doesn't hung on deadlock in "legit" import anymore ;-) Victor
- Previous message (by thread): [Python-Dev] Design Philosophy: Performance vs Robustness/Maintainability
- Next message (by thread): [Python-Dev] Design Philosophy: Performance vs Robustness/Maintainability
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list