You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=Nonecreated_at=<Date2015-12-17.20:18:44.779>labels= ['extension-modules', 'type-feature']
title='array.array accepting byte-order codes in format strings'updated_at=<Date2015-12-17.20:18:44.779>user='https://bugs.python.org/Zoinkity'
I'd like to propose allowing the use of byte-order characters in the typecode string used by the array.array class.
This removes any ambiguity on the order of the data, especially when that data is not known and loaded from an outside source. You wouldn't need to presume little or big endian machine byteorder or test the system to determine this. Also, it removes the necessity of byteswapping data that isn't in the correct order.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: