Message149550
> 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. |
|
Date |
User |
Action |
Args |
2011-12-15 13:11:36 | pitrou | set | recipients:
+ pitrou, amaury.forgeotdarc, orsenthil, vstinner, benjamin.peterson, ezio.melotti, Trundle, Mark.Shannon, davide.rizzo, python-dev |
2011-12-15 13:11:36 | pitrou | link | issue12149 messages |
2011-12-15 13:11:36 | pitrou | create | |
|