[Python-Dev] SVN rev. 85392 broke module handling in py3k (original) (raw)
Benjamin Peterson benjamin at python.org
Fri Oct 22 17:06:10 CEST 2010
- Previous message: [Python-Dev] SVN rev. 85392 broke module handling in py3k
- Next message: [Python-Dev] SVN rev. 85392 broke module handling in py3k
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2010/10/22 Antoine Pitrou <solipsis at pitrou.net>:
On Fri, 22 Oct 2010 09:41:09 -0500 Benjamin Peterson <benjamin at python.org> wrote:
2010/10/22 <exarkun at twistedmatrix.com>: > Instances of classes don't refer to the module their class is defined in. > It seems more likely that the reason the module is garbage collected is > that there really is nothing which refers to it anymore.
Indeed, this is really a Python bug, but there's no good way to deal with it unless dictionaries can know they are module globals. How about making functions keep a reference to the module they're defined in? Is there any reason we shouldn't do that?
I thought of that, too. It wouldn't be trivial to implement, though, and wouldn't solve the problem of clearing globals to avoid references cycles.
-- Regards, Benjamin
- Previous message: [Python-Dev] SVN rev. 85392 broke module handling in py3k
- Next message: [Python-Dev] SVN rev. 85392 broke module handling in py3k
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]