Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nmsg_msgtype.pyx: added types member with list of all available message types #9

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

hstern
Copy link
Contributor

@hstern hstern commented Feb 27, 2014

This is not functionally necessary but it will make nmsg easier to use. I've added a dictionary of vendors and msg types. A user can see which message types are available with code like this:

import nmsg
for vname,mnames in nmsg.msgtype.types.items():
    for mname in mnames:
        print '%s.%s' % (vname, mname)

@edmonds
Copy link
Contributor

edmonds commented Mar 17, 2014

hm, i'd prefer to put this outside of the nmsg.msgtypes.* namespace, actually. but in general i like the idea of being able to get at the vendor / message type ID mappings somehow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants