Nick Coghlan added the comment: I suspect if we'd thought of it back in the 3.0 or 3.1 time frame then giving the Py3 None a consistent "sorts low" behaviour would have been more likely.
At this stage of the Py3 life cycle, though, it seems simpler overall to remain consistent with earlier Py3 releases. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue20630> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
