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
Hi. Thanks for the bug report, that's really useful.
It looks like the initial and final two bits have been lost somehow. I'm away this week so can't debug what's happening here, but I'll take a proper look and get a fix in when I'm back.
This is a general problem when converting LSB0 slices with a negative step into their equivalent MSB0 slices, which can cut off some bits in some cases.
I'll add a fix soon , which will be in the next point release
When
bitstring.options.lsb0 == False
,bitstring.BitArray('0xf0a')[::-1][::-1]
returnsBitArray('0xf0a')
.However, when
bitstring.options.lsb0 == True
,bitstring.BitArray('0xf0a')[::-1][::-1]
returnsBitArray('0xc2')
.The text was updated successfully, but these errors were encountered: