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 serhiy.storchaka
Recipients abarry, berker.peksag, mark.dickinson, martin.panter, serhiy.storchaka, socketpair
Date 2016-07-28.06:03:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1469685816.35.0.90778274358.issue27638@psf.upfronthosting.co.za>
In-reply-to
Content
I agreed with Martin. The "host" byte order is sys.byteorder, and the "net" byteorder is just "big". There is one obvious way to specify this, and there is not need to add yet one way.

Adding support of new values for byteorder would complicate and slow down the code. int.to_bytes() and int.from_bytes() already are slower then struct.pack() and struct.unpack(), and parsing the byteorder argument is the main culprit here (see also issue27574).

I'm for rejecting this idea.
History
Date User Action Args
2016-07-28 06:03:36serhiy.storchakasetrecipients: + serhiy.storchaka, mark.dickinson, socketpair, berker.peksag, martin.panter, abarry
2016-07-28 06:03:36serhiy.storchakasetmessageid: <1469685816.35.0.90778274358.issue27638@psf.upfronthosting.co.za>
2016-07-28 06:03:36serhiy.storchakalinkissue27638 messages
2016-07-28 06:03:36serhiy.storchakacreate