- Fix broken sdist packaging. (#22)
- Use dials-data release for test data, instead of experimental branch. (#17)
- Added PEP-484 type hints for
pycbf.Img
, and mark as typing-compatible. (#20) - Windows is now a supported target. (#21)
- #18
- Prevent source files from being scattered across site-packages (#14)
- Added initial bindings for
libimg
. Only the methods required for minimal mar345 image reading have been implemented. (#1) - Add python bindings
read_buffer
forcbf_read_buffered_file
, for loading files directly from bytes buffers. (#3) - Functions that accept string arguments will now accept both
bytes
andstr
, for easier transition away fromSWIG_PYTHON_BYTE_CHAR
. (#4) - The
pycbf.cbf2str
utility function has been added to convert CBF string returns to str, no matter what is used in the SWIG bindings. (#4) - Add
pycbf.HAS_SWIG_PYTHON_STRICT_BYTE_CHAR
, to tell if the module has been build with theSWIG_PYTHON_STRICT_BYTE_CHAR
compile definition. (#10)
- Drop support for Python 2.7 (#5)
- Regeneration via nuweb literate sources is removed. The generated sources are now used as the original versions, which makes it much easier to add changes without building up stacks of patches. (#9)
- dials-data is now used for regression test data. (#6)
- A convenience script,
make_release.sh
, has been added to aid release generation. (#11)
This was an unreleased internal commit.
- Regenerated SWIG bindings for Python 3 compatibility
- Compiled with SWIG_PYTHON_STRICT_BYTE_CHAR
- Initial release of separated pycbf from CBFlib