Auto-tools/Projects/Pulse: Difference between revisions

Jump to navigation Jump to search
→‎Let's Use It: mozillapulse moved to GitHub
m (clarify that clientId part of exchange matches the user binding to the server)
(→‎Let's Use It: mozillapulse moved to GitHub)
Line 127: Line 127:
== Python Pulse client library ==
== Python Pulse client library ==


The [https://hg.mozilla.org/automation/mozillapulse/ mozillapulse] Python package provides classes for existing publishers, consumers, and messages so you can quickly build Pulse applications.  See the [https://hg.mozilla.org/automation/mozillapulse/file/tip/README.md README] to get started (although note that the test publisher is currently offline; see {{bug|1218976}}.  You can use another consumer, e.g. BuildConsumer, to verify your setup.).
The [https://github.com/mozilla-services/mozillapulse mozillapulse] Python package provides classes for existing publishers, consumers, and messages so you can quickly build Pulse applications.  See the [https://github.com/mozilla-services/mozillapulse/blob/master/README.md README] to get started (although note that the test publisher is currently offline; see {{bug|1218976}}.  You can use another consumer, e.g. BuildConsumer, to verify your setup.).


This library is somewhat inflexible, however, and should be rewritten. One idea is to turn TaskCluster's Python client into a standalone package.
This library is somewhat inflexible, however, and should be rewritten. One idea is to turn TaskCluster's Python client into a standalone package.
Confirmed users
1,927

edits

Navigation menu