On 08/16/2018 06:22 PM, Michal Novotny wrote: > On Thu, Aug 16, 2018 at 4:34 PM Jeremy Cline <jeremy@xxxxxxxxxx> wrote: >> >> So, am I right in saying your main objection is the Python package? Or >> do you object to then packaging that as an RPM? >> > > I don't really have any objections. I would just like to be able to read > messages as simple language-native structures and don't depend on > anything else than the base messaging framework when publishing or > receiving messages. Okay. You can do that now. There's a base Message class whose only schema restriction is that the message is a JSON object. You're free to use that and access the JSON directly, or to use an AMQP client directly (as long as you follow the same on-the-wire format). Just be aware that any messages you send that way will integrate poorly (or not at all) with services like notifications. I really don't recommend this approach since we've been down this path before and it's worked rather poorly, but I also don't want these tools to be a burden. -- Jeremy Cline XMPP: jeremy@xxxxxxxxxx IRC: jcline _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx/message/KQLKZWWXQZERINUG7NFI5HHWFP6PDRUB/
