gmr/pamqp

Issues

• Cannot specify negative consumer priority

  #45 opened 2 years ago by ralbertazzi
  7

• unmarshal heartbeat issue

  #53 opened 9 months ago by faxioman
  1

• Deprecation warning about `datetime.utcfromtimestamp`

  #51 opened a year ago by decaz
  2

• Over strict validation of queue/exchange name

  #47 opened a year ago by shayc-code
  2

• Unused variable

  #46 opened a year ago by decaz
  1

• Please upload a wheel release to pypi

  #43 opened 2 years ago by gilbahat
  3

• Unnecessary `Optional` typing

  #38 opened 3 years ago by decaz
  1

• Too strict DOMAIN_REGEX for exchange and queue naming

  #41 opened 2 years ago by deschmih
  4

• Decoding error

  #32 opened 3 years ago by vazir
  1

• Add support for Python3.9

  #34 opened 3 years ago by erikseulean
  2

• Unable to create queue with name containing semi column

  #36 opened 3 years ago by tvallois
  1

• Add branch for 2.x releases

  #28 opened 4 years ago by eandersson
  2

• When publishing a header with number between 129-255 a 2's complement number is published

  #27 opened 4 years ago by shoham-b
  5

• FAIL: test_basic_properties (test_frame_unmarshaling.DemarshalingTests)

  #26 opened 4 years ago by eLvErDe
  3

• Potential pamqp 3.0.0a5 codegen default issue

  #22 opened 5 years ago by gmr
  2

• RabbitMQ max queue length is 255 not 127

  #24 opened 5 years ago by dzen
  3

• 3.0.0a3: default can't be marshaled for non-specified int without default

  #20 opened 5 years ago by gmr
  0

• Use warning.warn() instead of raising DeprecationWarning

  #12 opened 6 years ago by dzen
  1

• Three failed tests on i586 and armv7l in decoding_tests.CodecDecodeTests class

  #11 opened 6 years ago by mcepl
  8

• Create a base PAMQP exception type that all others extend from

  #4 opened 6 years ago by gmr
  1

• Decoded field tables have byte string keys in Python3

  #6 opened 6 years ago by everilae
  1

• Either wrong struct format or range for short integer encoding

  #7 opened 6 years ago by everilae
  1

• Inconsistent unicode behaviour between python2 and 3

  #9 opened 6 years ago by everilae
  2

• Table integer should use inclusive ranges

  #10 opened 6 years ago by everilae
  1

• Short int encoder will not accept long values in python2

  #8 opened 6 years ago by everilae
  1

• Headers with byte values gets sent as strings which causes double encoding errors when other clients tries to decode it.

  #3 opened 10 years ago by Gyllsdorff
  3

• encoder.py tries to decode bytearray using UTF-8 even when the data is just a mix of bytes

  #2 opened 10 years ago by Gyllsdorff
  0

• Add support for the RabbitMQ/QPID byte array field type.

  #1 opened 10 years ago by gmr
  2