Resolved problem with import of int_sockopts which were moved from core to sugar

[vlcinsky]

With pyzmq 13.*, int_socopts were moved from zmq.core.constants to zmq.sugar

This caused failure to run if the system contained newer version of pyzmq.

[owend]

Bump? Seems like zmqc is pretty much useless without this... To be more clear, with a fresh install on ubuntu, I get this error:

$ zmqc -rc SUB 'tcp://localhost:5555'
Traceback (most recent call last):
File "/usr/local/bin/zmqc", line 9, in
load_entry_point('zmqc==0.1.0', 'console_scripts', 'zmqc')()
File "/usr/local/lib/python2.7/dist-packages/zmqc.py", line 286, in main
sock_opts = get_sockopts(args.sock_opts)
File "/usr/local/lib/python2.7/dist-packages/zmqc.py", line 227, in get_sockopts
int: set(zmq.core.constants.int_sockopts).union(
AttributeError: 'module' object has no attribute 'int_sockopts'

[vlcinsky]

Exactly. I found zmqc very valuable tool, allowing me to pass realtime various kind of messages across globe just calling this nice command.
Zachary seems to be alive and active in some areas, so we may hope, he will accept the pull request and make this trivial change available on pypi.
Until then, you may install from my clone.

[vlcinsky]

@zacharyvoase: is there any chance, you would accept this pull request? Or reject?
Is there anything I could do about your great zmqc utility? It is very simple but powerful tool, so I would even volunteer taking over care of the zmqc package, if it would sound acceptable to you.
Simple installation over

$ pip install zmqc

is nice and practicat, without your step forward I would have to instruct my colleagues to install over git, what is less ideal solution.
Looking forward to your reaction.

[mloughran]

+1, this works for me

[amckinley]

+1, I was about to put up the same pull request. Really need to get this merged!

[zacharyvoase]

If anyone wants to take over this project I'd be happy to make them an admin on the Github repo. I can't really maintain zmqc these days :-/

[amckinley]

Sure, I can do that!

[vlcinsky]

I volunteer too. zmqc is really my daily swiss army knife and would be happy to keep it in such a shape, users could use it as easily as telnet. Also have few ideas for extending it (there is couple of new socket types since it was written) but I do not want to overpromise.

For me it is not important, that I am the maintainer, but that the zmqc can be updated on pypi in timely manner, so if someone else like@amckinley is feeling to be ready to react to possible pull requests within few weeks, I would be happy with that.

This leads to additional request - hand over (or allow to share) publishing to pypi.

[zacharyvoase]

The PyPI one seems to be a lot harder…I need to figure out what I can do to delegate access to that.

[vlcinsky]

@zacharyvoase Quick search did not show direct answer, but my feeling, that some packages are having multiple owners seems correct, e.g.: https://pypi.python.org/pypi/zuul/2.0.0

Anyway, I appreciate your will to move on with zmqc, I am sure many users will find again the power hidden in such simple tool.

[vlcinsky]

@zacharyvoase

To set another person as Owner or Maintainer of PyPi package

To allow myself updating zmqc on pypi, the process goes as follows:

1. go to https://pypi.python.org
2. log into your account
3. pick the zmqc package (right top part of the screen)
4. select option "roles"
5. add myself (as vlcinsky) with "Maintainer" role.
6. submit
7. let me know you are done

Testing the role procedure on bflmpsvz package

I did test this procedure (using my accounts vlcinsky and jan.vlcinsky on package https://pypi.python.org/pypi/bflmpsvz/0.1.1

If you like, you may clone the package from https://github.com/vlcinsky/bflmpsvz, update and publish an update (but before let me know your account name on pypi)

On PyPi I have tried giving access to bflmpsvz for disturbyte, zacharyvoase and zachary.voase but all have reported "user name not known".

My plans with zmqc package on pypi

1. publish version zmqc 0.1.1 (see master tip of this repository where it is already pulled)
2. Possibly make the package compatible with Python 3
3. Possibly convert the setup.py to use pbr (to make versioning based on git tags)

All the time I want to:

1. keep the UNLICENSE "License"
2. keep you as package author (possibly adding myself somewhere around).

Let me know if you have any objections, want me to consult with you all these changes or you simply let me follow up with the great zmqc package in any way I find practical without bothering you.