Initial fork setup

[davidhewitt]

I've created this fork from https://github.com/awestlake87/pyo3-asyncio as a result of the conversation in awestlake87/pyo3-asyncio#126

It seems like the original pyo3-asyncio maintainer is currently unavailable, so here we can carry on their efforts and build upon them. (Andrew - if you read this, thank you for all your work and if you'd like to have access to push to this repository, please just ping.)

@Andrapyre, @regularkevvv, @cjdsellers - thanks very much for your offers to help out here. I've given you write access to the repository. If you've changed you minds (or don't ack this within, say, a month) I can revert that.

I can try to offer review and occasional pushes (much like I do for rust-numpy), however I'm quite stretched between upstream PyO3 maintenance and personal responsibilities, so I may be unreliable / a bit slow at times. I will do the releases in the short term with the goal would be delegate full autonomy to you folks in the mid term, if you're ok with that!

Repository setup steps:

• Complete cleanup / rename to pyo3-async-runtimes (I've just done the minimum to publish to crates.io)
• Upgrade to PyO3 0.22
• CI needs fixing for older Python versions / arm macOS
• CI needs fixing for MSRV
• Bump syn from 1 to 2 (Update syn requirement from 1 to 2 #4 - needs fixing)
• ... anything else?

[davidhewitt]

I tried to enable CI but looks like it's bit rotted a little... #6

[davidhewitt]

I added notes for MSRV CI and older Python versions / arm macOS.

Are we agreed to drop 3.7 and 3.8 support? For arm macOS I can copy over configuration from the PyO3 repository to get it working.

[regularkevvv]

Amazing! Thanks @davidhewitt , I think the invitation expired, could you please send it again?

[davidhewitt]

Done 👍