Message312178
| Author | ncoghlan |
|---|---|
| Recipients | cheryl.sabella, cvrebert, josh.r, martin.panter, ncoghlan, pitrou, rhettinger, scoder |
| Date | 2018-02-14.18:08:28 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1518631708.89.0.467229070634.issue20632@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Allowing for None-first and None-last ordering is a fair use case, but I'm not sure a __key__ protocol is the right answer to that - as your own example shows, it gets tricky when dealing with nested containers. It may make sense to raise the question on python-ideas for Python 3.8+, though, with Python-side ordering of database records as the main motivating use case. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2018-02-14 18:08:29 | ncoghlan | set | recipients: + ncoghlan, rhettinger, pitrou, scoder, cvrebert, martin.panter, josh.r, cheryl.sabella |
| 2018-02-14 18:08:28 | ncoghlan | set | messageid: <1518631708.89.0.467229070634.issue20632@psf.upfronthosting.co.za> |
| 2018-02-14 18:08:28 | ncoghlan | link | issue20632 messages |
| 2018-02-14 18:08:28 | ncoghlan | create | |