Terry J. Reedy added the comment: The warning, which became a failure in 3.6, was averted for 3.6 by #27372. I intentionally did not patch 3.5 and merge forward because the warning was neither unique nor a failure, while adding the merge would have been a considerable bother. Also, I anticipated that the 3.5.3 release after 3.6.0 would be the last 3.5 bugfix release as per normal policy, so that this would be a moot point by now. (And I have no idea why normal policy was not followed.) I think this issue should be closed as any of "duplicate", "out of date", or "won't fix".
---------- assignee: terry.reedy -> _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue30233> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
