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 martin.panter
Recipients abarry, martin.panter, socketpair
Date 2016-07-28.04:50:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1469681439.32.0.536283281317.issue27638@psf.upfronthosting.co.za>
In-reply-to
Content
I wouldn’t mind the “host” byte order, assuming it just means use sys.byteorder. I think I have done this a few times, both when I really wanted the native byte order, and when I didn’t care, but assumed the native order might be slightly more efficient (e.g. bitwise arithmetic on 512-byte blocks).

But I don’t understand the point of “net” byte order. Wouldn’t it be the same as “big”?
History
Date User Action Args
2016-07-28 04:50:39martin.pantersetrecipients: + martin.panter, socketpair, abarry
2016-07-28 04:50:39martin.pantersetmessageid: <1469681439.32.0.536283281317.issue27638@psf.upfronthosting.co.za>
2016-07-28 04:50:39martin.panterlinkissue27638 messages
2016-07-28 04:50:39martin.pantercreate