Handle dtypes like =d correctly.

[chpatrick]

"info.format" can contain either "d" or "=d" for native endianness, this handles that case.

[dancergraham]

Hello this seemed to fail but the logs are now longer available to explain why - do you recall what the problem was ?
Thanks,

[dancergraham]

ahh I'm starting to understand the vocabulary here - this is describing buffer format descriptors, right https://docs.python.org/3/library/struct.html

[dancergraham]

from reading the documentation it seems to me that =d and d are not necessarily the same - d would use standard size, whereas =d would use platform dependent c native size. I don't know enough about the different sizes of these data types on different platforms to know whether these differences are significant in practice ?

[dancergraham]

Hello @chpatrick can you provide any more information on this - are specific scanners generating files with =d ?

[chpatrick]

The format string here depends on what Python decides for the buffer you provide, not the scanner. I'm not sure what the best thing is to do regarding the size.

[dancergraham]

OK the tests pass I'm merging it like this for now and interested to read up some more on the subject. If you have any code which generates =d codes then I'm interested in trying it on both Windows and Linux to make sure it works OK