Antoine Pitrou <pit...@free.fr> added the comment: > Of course, I'd be all for changing local_getattro/local_setattro > to not need _ldict to make that guarantee! _ldict always *returns* > the correct pointer; it would be nice to make use of that somehow.
Indeed. Therefore, perhaps we could break the problem in two: - fix the reference leak by using the correct assignment idiom outlined earlier - fix local_getattro / local_setattro to always use the proper dict, regardless of thread switches ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue3710> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
