Message149550
| Author |
pitrou |
| Recipients |
Mark.Shannon, Trundle, amaury.forgeotdarc, benjamin.peterson, davide.rizzo, ezio.melotti, orsenthil, pitrou, python-dev, vstinner |
| Date |
2011年12月15日.13:11:36 |
| SpamBayes Score |
9.463019e-10 |
| Marked as misclassified |
No |
| Message-id |
<1323954674.3345.2.camel@localhost.localdomain> |
| In-reply-to |
<4EE9E632.7010805@hotpy.org> |
| Content |
> 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. |
|