Message253141
| Author |
eric.snow |
| Recipients |
eric.snow, rhettinger, serhiy.storchaka |
| Date |
2015年10月17日.21:10:07 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CALFfu7DDr9iyzxAQFKxWXA6ni=rO5YSTDDB5Ggi-hwgxpct+LA@mail.gmail.com> |
| In-reply-to |
<4304260.CpbrLUAp50@raxxla> |
| Content |
> Backward compatibility related to __class__ assignment was already broken in C
> implementation. In 3.4 following code works:
[snip]
> In 3.5 it doesn't.
Depending on what feedback we get from python-dev, that may need to be
fixed. I'd be inclined to not worry about it. :)
> No, this assignment is forbidden (due to #24912). You can't set __class_ for
> an instance of a subclass of non-heap type.
Ah, I see. So the solution to that issue has *forced* a compatibility break.
> Could you please raise a discussion on Python-Dev? You will formulate the
> problem better.
I will. |
|