- Full cleanup of all the docs
- General sphinx housekeeping
- Updated all the old/bad links
- More reliable tests
- Updated Changelog
- Removed dead/deprecated code
- Added documentation generation test
- Includes some test stabilization
- Fixes manylinux2010 build issues (linker flag order due to old gcc)
- More rigorous python setup.py clean
- Requires capnproto v0.8.0 or greater
- Including system libcapnp include path for import (e.g. import
stream_capnp)
- Bundle libcapnp .capnp files when not using system libcapnp
- Removing more distutils usage. Now using pkg-config to determine the
system version of libcapnp (mainly for Linux, but should work on macOS
with brew)
- Removed dead code
Resolves issues #215#216#217
Lots of fixes for Issue #218 (all sorts of retry methods needed for
GitHub Actions)
- Validates that the manylinux2010 environment can build pycapnp
- Handle lib and lib64 cases
- Has patch for aligned_alloc symbol (not available prior to glibc 2.16)
https://github.com/capnproto/capnproto/issues/743
- Fixes#197
- Should be ready to prepare a v1.0.0b1 release
- Basic tests are working
- May need some adjustments to get all tests working
- Cleaned up bundling to take Python arch into account when building
with multiple architectures
- Breaking some earlier compatibility to cleanup build messages
- As well as being able to publish pypi releases
* Builds can be complicated to package correctly
- Windows support
flake8 . --count --exit-zero --max-complexity=10 --max-line-length=127 --statistics --exclude benchmark
Excluding the benchmark directory (due to protobuf generated files)
Also removing some Python2 specific code
The current logic unconditionally tries to build /and run/ a small
executable linked against libcapnp. The 'run' step is ostensibly
to get the current library version number, however this number isn't
actually used anywhere.
More importantly, this breaks cross-compiling completely as in that
mode you can't run an executable that's just been built.
One option would be to fix the build scripts for cross-compiling but
this is relatively complex. This patch implements a simple change
that basically boils down to '--force-system-libcapnp' actually
forcing that, skipping the build and run tests. The assumption is
that if you're cross-compiling then you're most likely to be building
the library yourself anyway and if you're specifying that flag, then
you know what you're doing.
