-
Notifications
You must be signed in to change notification settings - Fork 844
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move to use pamqp for core AMQP related work #645
Labels
Milestone
Comments
Is this still desirable? pamqp hasn't been active since 2015 and using pamqp would introduce an external dependency into pika core. |
I do try and keep it up to date, and the goal was to strip down the behaviors, but I'll close this since it was more for me to maintain spec stuff in one spot. If the project wants to do so going forward, that's cool, but I won't leave it as a to-do. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Move to using pamqp for the core AMQP functionality provided in
pika.frame
,pika.spec
,pika.compat
, and in some casespika.exceptions
.The text was updated successfully, but these errors were encountered: