This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

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 <>
In-reply-to <4304260.CpbrLUAp50@raxxla>
> Backward compatibility related to __class__ assignment was already broken in C
> implementation. In 3.4 following code works:
> 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.
Date User Action Args
2015-10-17 21:10:07eric.snowsetrecipients: + eric.snow, rhettinger, serhiy.storchaka
2015-10-17 21:10:07eric.snowlinkissue25410 messages
2015-10-17 21:10:07eric.snowcreate