Message291411
> I'm inclined not to attempt to fix this. The reason that we don't pull 'a.b' out of sys.modules at this point is that if later in the execution of a/b.py we get an exception, the import will be cancelled, and sys.modules['a.b'] will be *deleted*, and then the variable 'c' would have a reference to a half-loaded module.
I think this is solvable -- track and delete the references too.
It's your decision in the end, but I think it's not good to make the language inconsistent because of technical limitations -- the interface should be the primary source for decisions. |
|
Date |
User |
Action |
Args |
2017-04-10 05:29:39 | Victor.Varvariuc | set | recipients:
+ Victor.Varvariuc, gvanrossum, barry, brett.cannon, ncoghlan, THRlWiTi, eric.snow |
2017-04-10 05:29:39 | Victor.Varvariuc | set | messageid: <1491802179.84.0.513231600867.issue30024@psf.upfronthosting.co.za> |
2017-04-10 05:29:39 | Victor.Varvariuc | link | issue30024 messages |
2017-04-10 05:29:39 | Victor.Varvariuc | create | |
|