This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients dfrojas, eli.bendersky, rhettinger, scoder, serhiy.storchaka, taleinat
Date 2018-10-27.03:16:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1540610207.08.0.788709270274.issue34160@psf.upfronthosting.co.za>
In-reply-to
Content
Though it is compatible with earlier versions, I don't see any reason to keep sorting at all, especially as a default.  The reasonable default is that whatever order the user specifies is what the tool does.

The backwards compatible argument is specious.  The ordering was never guaranteed.  The only reason that we had sorting was to make the XML generation deterministic, and that is something we would still have.

I vote against the permanent API expansion with an unhelpful default.  The sorting is no longer necessary or desirable.  Appropriately, we never guaranteed it, leaving us the implementation flexibility to make exactly this change.

AFAICT, no XML user has ever expressed an interest in having attributes appear in alphabetical order -- for that matter, I can't recall any HTML user having expressed this preference (instead, they prefer to put class and id tags ahead of other tags for example).
History
Date User Action Args
2018-10-27 03:16:47rhettingersetrecipients: + rhettinger, scoder, taleinat, eli.bendersky, serhiy.storchaka, dfrojas
2018-10-27 03:16:47rhettingersetmessageid: <1540610207.08.0.788709270274.issue34160@psf.upfronthosting.co.za>
2018-10-27 03:16:47rhettingerlinkissue34160 messages
2018-10-27 03:16:46rhettingercreate