Message298098
Based on https://github.com/python/cpython/pull/2646/files#r126574323, I'm actually thinking along different lines: I'm starting to think we should move the current sys.modules to sys._modules, and make sys.modules a synchronised wrapper that does the following for all get/set/delete operations:
# Acquires the global import lock
# Acquires the relevant module lock
# Releases the global import lock
# Mutates sys._modules
# Releases the module lock
That said, I'm not sure that would be sufficient to give the desired level of atomicity, so exposing ModuleLockManager may actually be a better approach. |
|
Date |
User |
Action |
Args |
2017-07-11 01:22:17 | ncoghlan | set | recipients:
+ ncoghlan, brett.cannon, eric.snow |
2017-07-11 01:22:17 | ncoghlan | set | messageid: <1499736137.19.0.973776620292.issue30893@psf.upfronthosting.co.za> |
2017-07-11 01:22:17 | ncoghlan | link | issue30893 messages |
2017-07-11 01:22:16 | ncoghlan | create | |
|