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 eli.bendersky, rhettinger, scoder, serhiy.storchaka, taleinat
Date 2018-10-25.17:10:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Consider this as a feature request.  It is perfectly reasonable for a user to want to generate specific XML output and to want to control the order that the attributes are listed.  It is perfectly reasonable for the API to preserve the order that the user specified rather than change it into some other order that they either don't expect or can't control.  Starting in Python 3.6, the language guarantees that the order of keyword arguments is preserved.  Knowing that, it will be natural for users to start viewing as buggy APIs that discard that order when everything else in the eco-system respects the ordering.

When I teach ElementTree in Python courses, students notice this behavior and ask why the order was swapped.  My only answer is that we didn't used to have a way to control it, so the input order was ignored (i.e. a reason that no longer makes sense).
Date User Action Args
2018-10-25 17:10:00rhettingersetrecipients: + rhettinger, scoder, taleinat, eli.bendersky, serhiy.storchaka
2018-10-25 17:10:00rhettingersetmessageid: <>
2018-10-25 17:10:00rhettingerlinkissue34160 messages
2018-10-25 17:10:00rhettingercreate