R. David Murray added the comment: The behavior of s.type has changed in 3.5: it now behaves like the proposed new method behaves. Looking at the source I can't figure out why this is so. It doesn't seem as though it should be, but this needs to be sorted out before we can proceed.
---------- nosy: +ethan.furman _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue21327> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
