pycapnp v1.0.0b2 released

[Jacob Alexander]

https://pypi.org/project/pycapnp/1.0.0b2/

https://github.com/capnproto/pycapnp/releases/tag/v1.0.0b2

I've been trying to get everything ready for a v1.0.0 release, unfortunately there's still one last issue before I feel comfortable with a v1.0.0.

It's a new issue that may be related to the GitHub Actions environment for testing, though it could be an issue with libcapnp itself (https://github.com/capnproto/pycapnp/issues/222). The exception is strange because I don't think there's a problem with the actual test code (capnproto-0.7.0 and capnproto-0.8.0 have the same issue).

The main change for 1.0.0b2 (from b1) is capnproto-0.8.0 support and updating the documentation (https://capnproto.github.io/pycapnp). I've spent quite a bit of time on the Quickstart (along with the rest of the documentation). I debated having multiple versions of the documentation, but this is rather tricky to do in an automated fashion because sphinx needs the binary module of pycapnp for each version of documentation generated. For now I'll probably just stick with generating new documentation for each release.

Changelog

• Minimum capnproto version is now 0.8.0
• Added asyncio ssl calculator test
• Added poll_once to TwoPartyServer API
• More cleanup
• Fix absolute and circular imports
• Fix Promise aliasing issue (Promise to \_Promise)
• Documentation update
• Updated installation instructions
• Added RPC documentation for asyncio

The previous issue holding up the release I've waived https://github.com/capnproto/pycapnp/issues/196 as it only seems to affect getTimer on Windows (which is a wrapper for libcapnp). Instead I've added another test case to exercise asyncio functionality on Windows. My suspicion is that something is starving/cancelling an event loop inside libcapnp related to the timer.

Remaining issues can be found here: https://github.com/capnproto/pycapnp/projects/2

Hopefully I'll be able to figure out the last issue and finally release v1.0.0!

-HaaTa / Jacob Alexander