Raymond Hettinger <raymond.hettin...@gmail.com> added the comment:
I prefer option 5 and leaving the module as-is. The bisect module api is slice oriented and, in general, people have a hard time reasoning about slices for reverse ordered sequences. Even the forward ordered API is a bit awkward so that we had to document how to implement find_lt(), find_le(), etc. because it wasn't obvious how to do so. Also, it doesn't seem to come-up much (the bisect module is over two decades old). So, I don't think the API and the internals should be gummed up for this. My vote is -1 because it would cause more problems than it would solve. Let's cater to the common use cases rather than every possible variant. ---------- nosy: +rhettinger _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue43300> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
