Message387540
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. |
|
Date |
User |
Action |
Args |
2021-02-22 19:56:37 | rhettinger | set | recipients:
+ rhettinger, mCoding |
2021-02-22 19:56:37 | rhettinger | set | messageid: <1614023797.24.0.738002287091.issue43300@roundup.psfhosted.org> |
2021-02-22 19:56:37 | rhettinger | link | issue43300 messages |
2021-02-22 19:56:37 | rhettinger | create | |
|