Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork366
allow roundtripping theBytesCodec#3417
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
keewis commentedAug 30, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
looks like some tests actually relied on this behavior, i.e. choosing the default endian if none was specified for multi-byte dtypes (even though this technically violates the spec). Since this might be potentially user facing (I'm not certain, but at least What wecould do is start a deprecation cycle by checking for this in |
Uh oh!
There was an error while loading.Please reload this page.
closes#3416
Basically, we're changing the default for
endianwhen constructingBytesCodecusingfrom_dict.(I also renamed
test_endian.pytotest_bytes.pyas mentioned in#3416 (comment))TODO:
Add docstrings and API docs for any new/modified user-facing classes and functionsNew/modified features documented indocs/user-guide/*.rstchanges/