Antoine Pitrou <pit...@free.fr> added the comment: > Since PyType_Modified is generally called whenever a type is modified, > it is likely to act as a guardian for any future optimisations that > require classes to be unchanged. > > Thus, given these two reasons, it seems wise to call PyType_Modified > anywhere the type is modified, however minor that modification appears > to be.
Well, unless we start reviewing all the places where a type might be directly modified, I'm not sure there's much point in adding PyType_Modified to those two. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue12149> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
