Import Error due to API Change in pamqp>=3.0.0 (specification -> commands)

[ltiannan]

Issue Description

When installing the latest amqpstorm (2.11.1) alongside pamqp>=3.0.0 (e.g., 3.3.0), an ImportError occurs. This is because pamqp renamed its specification module to commands starting from version 3.0.0, but amqpstorm still imports the old module name.

Error Message:
ImportError: cannot import name 'specification' from 'pamqp'

Root Cause

After inspecting the source code, I found that amqpstorm imports pamqp.specification in several files, such as amqpstorm/channel.py and amqpstorm/basic.py. According to the pamqp library's documentation, the public API modules were renamed in version 3.0.0:

• Old (pamqp < 3.0.0): from pamqp import specification
• New (pamqp >= 3.0.0): from pamqp import commands

Suggested Fix

Update the import statements in amqpstorm to be compatible with the newer pamqp API. This could be done by:

1. Direct update: Replace from pamqp import specification with from pamqp import commands in the relevant files.
2. Conditional import (for broader compatibility): Implement a try/except block to attempt importing the new name first, falling back to the old one. Example:

try:
    from pamqp import specification
except ImportError:
    from pamqp import commands as specification

[eandersson]

This is a known issue and there is a separate branch with a fix for this. If this is important to you I can look at publishing a release based on this branch that supports pamqp 3.0.0.
https://github.com/eandersson/amqpstorm/tree/main

[ltiannan]

这是一个已知问题，并且有一个单独的分支包含了修复程序。如果您对此问题很重视，我可以考虑基于此分支发布一个支持 pamqp 3.0.0 的版本。https ://github.com/eandersson/amqpstorm/tree/main

Hi eandersson,

Thank you very much for your prompt response and for having a fix ready in a separate branch. This is great to hear!

Yes, this issue is quite important for our/my project. The dependency conflict with pamqp>=3.0.0 currently blocks us from using other updated libraries in the ecosystem. Having an official release of amqpstorm that supports pamqp 3.0.0 would significantly resolve our environment compatibility issues and benefit others facing the same situation.

We would be very grateful if you could consider publishing a new release to PyPI based on the fix branch whenever it's convenient for you. This would make the upgrade path much smoother for all users.

Please let us know if there's anything we can do to assist, such as testing the branch in our environment or providing additional feedback. We truly appreciate your work on maintaining this valuable library.

Best regards,