There have been a number of deprecations/removals in trio since trio-amqp was last updated:
I will submit a PR shortly to address these changes.
There are also some existing similar updates in master (at least the removal of trio.Queue) that have yet to be released. As a result, the current release of trio-amqp is currently only compatible with trio<=0.8.0 (0.17.0 is current). Please make a new release as soon as possible. There's been no movement on releasing https://github.com/M-o-a-T/asyncamqp as mentioned in #8, and it sounds like you intend to instead merge that back into trio-amqp as discussed in #9, but the situation right now is that there is no working, released AMQP client library for recent versions of trio.
There have been a number of deprecations/removals in trio since
trio-amqpwas last updated:open_cancel_scope()deprecatedEvent.clear()deprecatedtrio.hazmatrenamed totrio.lowlevel(also as Updates needed for recent trio versions (0.17.0 current as of this writing) #11)I will submit a PR shortly to address these changes.
There are also some existing similar updates in
master(at least the removal oftrio.Queue) that have yet to be released. As a result, the current release oftrio-amqpis currently only compatible withtrio<=0.8.0(0.17.0 is current). Please make a new release as soon as possible. There's been no movement on releasing https://github.com/M-o-a-T/asyncamqp as mentioned in #8, and it sounds like you intend to instead merge that back intotrio-amqpas discussed in #9, but the situation right now is that there is no working, released AMQP client library for recent versions of trio.