Barry A. Warsaw added the comment: I'm not expecting a change either, I was also just documenting observed breakages. Given that I've ported a *ton* of code to 3.5 and only seen a handful of failures related to this issue, I agree that it's better just to provide information and let packages fix their code.
I am keeping a running document of such issues here: https://wiki.python.org/moin/PortingToPy3k/34to35 As for the larger question of doctests, we can discuss elsewhere. Probably not appropriate for *this* issue <wink>. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22032> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
