Skip to content

Python SDK for BlazingMQ, a modern high-performance open source message queuing system.

License

Notifications You must be signed in to change notification settings

bloomberg/blazingmq-sdk-python

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

46 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


BlazingMQ OS Linux OS MacOS License Python MessageQueue Documentation Code Style Supported Python versions

BlazingMQ Python SDK

This repository provides the official Python client library, as well as examples of how applications can interact with BlazingMQ. BlazingMQ is an open source message queue system, which focuses on efficiency, reliability, and a rich feature set. Please see the BlazingMQ repo and documentation for more details about BlazingMQ.

This Python client is fully supported by the BlazingMQ team, and we intend to provide feature and/or API parity with the BlazingMQ C++ client library.

Menu

Building

For instructions on how to build and test the package, check docs/BUILD.md.

Contributions

We welcome your contributions to help us improve and extend this project!

We welcome issue reports here; be sure to choose the proper issue template for your issue, so that we can be sure you're providing us with the necessary information.

Before sending a Pull Request, please make sure you have read our Contribution Guidelines.

License

The BlazingMQ Python SDK is Apache 2.0 licensed, as found in the LICENSE file.

Code of Conduct

This project has adopted a Code of Conduct. If you have any concerns about the Code, or behavior which you have experienced in the project, please contact us at [email protected].

Security Vulnerability Reporting

If you believe you have identified a security vulnerability in this project, please send an email to the project team at [email protected], detailing the suspected issue and any methods you've found to reproduce it.

Please do NOT open an issue in the GitHub repository, as we'd prefer to keep vulnerability reports private until we've had an opportunity to review and address them.