Skip to content
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

Open
gmr opened this issue Sep 2, 2015 · 3 comments · May be fixed by #1400
Open

Move to use pamqp for core AMQP related work #645

gmr opened this issue Sep 2, 2015 · 3 comments · May be fixed by #1400
Milestone

Comments

@gmr
Copy link
Member

gmr commented Sep 2, 2015

Move to using pamqp for the core AMQP functionality provided in pika.frame, pika.spec, pika.compat, and in some cases pika.exceptions.

@vitaly-krugl
Copy link
Member

vitaly-krugl commented May 3, 2018

Is this still desirable? pamqp hasn't been active since 2015 and using pamqp would introduce an external dependency into pika core.

@gmr
Copy link
Member Author

gmr commented Nov 7, 2018

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.

@gmr gmr closed this as completed Nov 7, 2018
@lukebakken lukebakken modified the milestones: 1.0, 2.0.0 Jun 28, 2022
@lukebakken lukebakken reopened this Jun 28, 2022
@lukebakken
Copy link
Member

@gmr The pamqp project appears active! I'm scheduling this for Pika 2.0

lukebakken added a commit that referenced this issue Nov 27, 2022
@lukebakken lukebakken linked a pull request Nov 27, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants