Message338107
| Author | rhettinger |
|---|---|
| Recipients | Mariatta, dfrojas, eli.bendersky, matrixise, nedbat, rhettinger, scoder, serhiy.storchaka, sivert, taleinat, vstinner |
| Date | 2019-03-16.22:46:24 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1552776384.81.0.303285437261.issue34160@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> Raymond, it sounds like your end-user didn't agree that
> "sorting is no longer necessary or desirable."
Sorry for being unclear. The user needed to *overcome* the sorting behavior so that they could produce an ordering of their own choosing. The problem then became that we had to work out a way to defeat the sorting to allow the requested attribute ordering to be preserved.
Roughly:
casefile = Element('casefile', clearance="confidential",
access="internal", valid_through="31 Mar 2022")
The desired result is that the attribute order be preserved. By removing the sort, a user can specify an order they want and have that specification honored. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-03-16 22:46:24 | rhettinger | set | recipients: + rhettinger, scoder, vstinner, taleinat, nedbat, eli.bendersky, serhiy.storchaka, matrixise, sivert, Mariatta, dfrojas |
| 2019-03-16 22:46:24 | rhettinger | set | messageid: <1552776384.81.0.303285437261.issue34160@roundup.psfhosted.org> |
| 2019-03-16 22:46:24 | rhettinger | link | issue34160 messages |
| 2019-03-16 22:46:24 | rhettinger | create | |