Message249607
| Author |
ncoghlan |
| Recipients |
Guido.van.Rossum, Mark.Shannon, benjamin.peterson, eltoder, gvanrossum, larry, lemburg, ncoghlan, njs, pitrou, rhettinger, serhiy.storchaka, vstinner |
| Date |
2015年09月03日.06:12:28 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1441260748.75.0.286931155773.issue24912@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I've filed issue 24991 to suggest reviewing the wider question of how we deal with identifying whether or not a type's instances are expected to be "truly immutable" in the Python 3.6 time frame.
For 3.5, I think Nathaniel's proposed patch restoring the assumption that non-heap types are immutable by default, and whitelisting __class__ assignment for PyModuleType specifically is a good way to resolve this with minimal code churn late in the release cycle. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2015年09月03日 06:12:28 | ncoghlan | set | recipients:
+ ncoghlan, lemburg, gvanrossum, rhettinger, pitrou, vstinner, larry, benjamin.peterson, njs, Mark.Shannon, eltoder, serhiy.storchaka, Guido.van.Rossum |
| 2015年09月03日 06:12:28 | ncoghlan | set | messageid: <1441260748.75.0.286931155773.issue24912@psf.upfronthosting.co.za> |
| 2015年09月03日 06:12:28 | ncoghlan | link | issue24912 messages |
| 2015年09月03日 06:12:28 | ncoghlan | create |
|