fedmsg.meta handles the conversion of fedmsg messages (dict-like json objects) into internationalized human-readable strings: strings like "nirik voted on a tag in tagger" and "lmacken commented on a bodhi update."
The intent is to use the module 1) in the fedmsg-irc bot and 2) in the gnome-shell desktop notification widget. The sky is the limit, though.
The primary entry point is fedmsg.meta.msg2repr() which takes a dict and returns the string representation. Portions of that string are in turn produced by fedmsg.meta.msg2title(), fedmsg.meta.msg2subtitle(), and fedmsg.meta.msg2link().
Message processing is handled by a list of MessageProcessors (instances of fedmsg.meta.base.BaseProcessor) which are discovered on a setuptools entry-point. Messages for which no MessageProcessor exists are handled gracefully.
The original deployment of fedmsg in Fedora Infrastructure uses metadata providers/message processors from a plugin called fedmsg_meta_fedora_infrastructure. If you’d like to add your own processors for your own deployment, you’ll need to extend fedmsg.meta.base.BaseProcessor and override the appropriate methods. If you package up your processor and expose it on the fedmsg.meta entry-point, your new class will need to be added to the fedmsg.meta.processors list at runtime.
End users can have multiple plugin sets installed simultaneously.
Bases: exceptions.Exception
Initialize all of the text processors.
You’ll need to call this once before using any of the other functions in this module.
>>> import fedmsg.config
>>> import fedmsg.meta
>>> config = fedmsg.config.load_config([], None)
>>> fedmsg.meta.make_processors(**config)
>>> text = fedmsg.meta.msg2repr(some_message_dict, **config)
Return a dict mapping of usernames to avatar URLs.
Return a dict mapping of usernames to email addresses.
Return a primary icon associated with a message.
Return a URL associated with a message.
Return a set of objects associated with a message.
“objects” here is the “objects” from english grammar.. meaning, the thing in the message upon which action is being done. The “subject” is the user and the “object” is the packages, or the wiki articles, or the blog posts.
Where possible, use slash-delimited names for objects (as in wiki URLs).
Return a set of package names associated with a message.
For a given message return the text processor that can handle it.
This will raise a fedmsg.meta.ProcessorsNotInitialized exception if fedmsg.meta.make_processors() hasn’t been called yet.
Return a human-readable or “natural language” representation of a dict-like fedmsg message. Think of this as the ‘top-most level’ function in this module.
Return a secondary icon associated with a message.
Return a ‘subtitle’ or secondary text associated with a message.
Return a ‘title’ or primary text associated with a message.
Return a set of FAS usernames associated with a message.
Bases: object
Base Processor. Without being extended, this doesn’t actually handle any messages.
Processors require that an internationalization_callable be passed to them at instantiation. Internationalization is often done at import time, but we handle it at runtime so that a single process may translate fedmsg messages into multiple languages. Think: an IRC bot that runs #fedora-fedmsg, #fedora-fedmsg-es, #fedora-fedmsg-it. Or: a twitter bot that posts to multiple language-specific accounts.
That feature is currently unused, but fedmsg.meta supports future internationalization (there may be bugs to work out).
Return a dict of avatar URLs associated with a message.
Return a dict of emails associated with a message.
If we can handle the given message, return the remainder of the topic.
Return a “icon” for the message.
Return a “link” for the message.
Return a set of objects associated with a message.
Return a set of package names associated with a message.
Return a “secondary icon” for the message.
Return a “subtitle” for the message.
Return a set of FAS usernames associated with a message.