More PY3 support for FormatPY, the xfel legacy image pickle format #205
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current dxtbx testing for FormatPY uses pickles that were created using py2. While reprocessing old LCLS data I regenerated some image pickles on a py3 build and found I couldn't read them because of encoding problems. This PR fixes that problem using a new function in iotbx/npy.py, image_dict_to_unicode.
Additionally, this makes the understand method of FormatPY more robust. Adds pickle protocol 4 magic bytes check but also tries to de-pickle the file, as the pickle magic bytes aren't guaranteed to fully specify whether a file is a pickle.
Note, the only place image pickles are generated in xfel land is averaging XTC streams with Rayonix data. Everyting else, including xtc_process using Rayonix data, uses cbfs.