Eric Snow added the comment: > 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25410> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
