2.0.10.1 pushed, tagged, registered, etc., replacing 2.0.10-1 for debian-ish reasons.<div><br></div><div>-MinRK<br><div><br><div class="gmail_quote">On Sun, Jan 30, 2011 at 11:16, Min RK <span dir="ltr"><<a href="mailto:benjaminrk@gmail.com">benjaminrk@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
<br>
On Jan 30, 2011, at 9:10, Brian Granger <<a href="mailto:ellisonbg@gmail.com">ellisonbg@gmail.com</a>> wrote:<br>
<br>
> Thomas,<br>
><br>
> Min and I were just talking about this yesterday. Here is our logic:<br>
><br>
> * We can't use 2.0.10a because pypi treats this as alpha and will see<br>
> 2.0.10 as a later version rather than earlier.<br>
> * We use the 2.0.10-1 notation for exactly the same reason that Debian<br>
> does - the 2.0.10 is an upstream version number and the -1 is our<br>
> variant of the 2.0.10 release.<br>
> * But, you are right, we had not thought about the Debian versioning<br>
> scheme that would lead to the very confusing 2.0.10-1-1.<br>
><br>
> Min, is there a problem with going with the 2.0.10.1 route? Will pypi<br>
> treat this version # correctly?<br>
<br>
</div>I'll check this afternoon, and push it as 2.0.10.1 if it doesn't object. As long as we are not complying with distutils StrictVersion, might as well play as nice with everyone else as we can.<br>
<font color="#888888"><br>
-MinRK<br>
</font><div><div></div><div class="h5"><br>
><br>
> Brian<br>
><br>
> On Sun, Jan 30, 2011 at 4:38 AM, Thomas Kluyver <<a href="mailto:takowl@gmail.com">takowl@gmail.com</a>> wrote:<br>
>> I've jumped in and updated the bug report.<br>
>><br>
>> I foresee confusion with the version numbering, however. Debian has called<br>
>> its package version 2.0.10-1, although it corresponds to what you released<br>
>> as 2.0.10. Debian package numbering uses "-n" suffixes to denote debian<br>
>> revisions of an upstream release. Can I suggest that you consider a<br>
>> different scheme for naming versions matching a particular ZMQ release,<br>
>> perhaps 2.0.10.1 or 2.0.10a?<br>
>><br>
>> Thanks,<br>
>> Thomas<br>
>><br>
>> On 30 January 2011 02:53, Brian Granger <<a href="mailto:ellisonbg@gmail.com">ellisonbg@gmail.com</a>> wrote:<br>
>>><br>
>>> Erik,<br>
>>><br>
>>> Thanks for doing this. We just released 2.0.10-1, which has a fix of<br>
>>> an important memory leak. Is there any chance you could update the<br>
>>> request to say they should use 2.0.10-1?<br>
>>><br>
>>> Here is the download page that has the release:<br>
>>><br>
>>> <a href="https://github.com/zeromq/pyzmq/downloads" target="_blank">https://github.com/zeromq/pyzmq/downloads</a><br>
>>><br>
>>> Thanks,<br>
>>><br>
>>> Brian<br>
>>><br>
>>> On Fri, Jan 28, 2011 at 8:30 PM, Erik Tollerud <<a href="mailto:erik.tollerud@gmail.com">erik.tollerud@gmail.com</a>><br>
>>> wrote:<br>
>>>> I've submitted a request that they bring in 2.0.10 for the final Natty<br>
>>>> - <a href="https://bugs.launchpad.net/ubuntu/+source/pyzmq/+bug/709089" target="_blank">https://bugs.launchpad.net/ubuntu/+source/pyzmq/+bug/709089</a> ... who<br>
>>>> knows if someone in the Universe will take the time to do it, but the<br>
>>>> request has been made, it least.<br>
>>>><br>
>>>> On Thu, Jan 27, 2011 at 2:24 AM, Thomas Kluyver <<a href="mailto:takowl@gmail.com">takowl@gmail.com</a>><br>
>>>> wrote:<br>
>>>>> I think Ubuntu might need to be prodded to update - according to the<br>
>>>>> release<br>
>>>>> schedule, automatic imports from Debian stopped at the end of December:<br>
>>>>> <a href="https://wiki.ubuntu.com/DebianImportFreeze" target="_blank">https://wiki.ubuntu.com/DebianImportFreeze</a><br>
>>>>><br>
>>>>> ZMQ itself is already at 2.0.10, so it should be a no-brainer to add<br>
>>>>> the<br>
>>>>> matching release of pyzmq.<br>
>>>>><br>
>>>>> Thomas<br>
>>>>><br>
>>>>> On 27 January 2011 01:11, Mark Voorhies <<a href="mailto:mark.voorhies@ucsf.edu">mark.voorhies@ucsf.edu</a>> wrote:<br>
>>>>>><br>
>>>>>> Naive googling suggests that the major Linux distros are ready for<br>
>>>>>> 2.0.10:<br>
>>>>>> (I know some of the packagers are on this list, so feel free to<br>
>>>>>> correct<br>
>>>>>> me)<br>
>>>>>><br>
>>>>>> Debian: 2.0.10 is in experimental (looks like it's being held there<br>
>>>>>> until<br>
>>>>>> after next week's release of Squeeze)<br>
>>>>>> <a href="http://packages.qa.debian.org/p/pyzmq.html" target="_blank">http://packages.qa.debian.org/p/pyzmq.html</a><br>
>>>>>><br>
>>>>>> Ubuntu: is still on 0.1.20100703+git18f5d06155-1 for Natty?<br>
>>>>>> <a href="https://launchpad.net/ubuntu/+source/pyzmq" target="_blank">https://launchpad.net/ubuntu/+source/pyzmq</a><br>
>>>>>> Reasonable to assume that 2.0.10 will propagate after it<br>
>>>>>> hits<br>
>>>>>> Debian unstable?<br>
>>>>>><br>
>>>>>> Fedora: 2.0.10 is in testing for Fedora 14<br>
>>>>>> <a href="https://admin.fedoraproject.org/updates/python-zmq" target="_blank">https://admin.fedoraproject.org/updates/python-zmq</a><br>
>>>>>><br>
>>>>>> SUSE: 2.0.10 is in SLE_11 (same as SLED?) and OpenSUSE 11.1<br>
>>>>>><br>
>>>>>><br>
>>>>>> <a href="https://build.opensuse.org/package/binaries?package=python-pyzmq&project=devel%3Alanguages%3Apython&repository=SLE_11" target="_blank">https://build.opensuse.org/package/binaries?package=python-pyzmq&project=devel%3Alanguages%3Apython&repository=SLE_11</a><br>
>>>>>><br>
>>>>>><br>
>>>>>> <a href="https://build.opensuse.org/package/binaries?package=python-pyzmq&project=devel%3Alanguages%3Apython&repository=openSUSE_11.1" target="_blank">https://build.opensuse.org/package/binaries?package=python-pyzmq&project=devel%3Alanguages%3Apython&repository=openSUSE_11.1</a><br>
>>>>>><br>
>>>>>> --Mark<br>
>>>>>><br>
>>>>>> On Wednesday, January 26, 2011 04:42:48 pm MinRK wrote:<br>
>>>>>>> 2.0.10 has a lot of stability improvements over previous releases.<br>
>>>>>>> The<br>
>>>>>>> main argument against it is if major distributions (EPD, various<br>
>>>>>>> Linux<br>
>>>>>>> distros) are still shipping 2.0.9, then we should maybe hold back.<br>
>>>>>>><br>
>>>>>>> I can easily change the import if we want to do that.<br>
>>>>>>><br>
>>>>>>> -MinRK<br>
>>>>>>><br>
>>>>>>> On Wed, Jan 26, 2011 at 16:12, Brian Granger <<a href="mailto:ellisonbg@gmail.com">ellisonbg@gmail.com</a>><br>
>>>>>>> wrote:<br>
>>>>>>><br>
>>>>>>> I mean require 2.0.10?<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> On Wed, Jan 26, 2011 at 4:12 PM, Brian Granger<br>
>>>>>>> <<a href="mailto:ellisonbg@gmail.com">ellisonbg@gmail.com</a>><br>
>>>>>>> wrote:<br>
>>>>>>> > Should we require 2.0.9 for IPython?<br>
>>>>>>> ><br>
>>>>>>> > Brian<br>
>>>>>>> ><br>
>>>>>>> > On Wed, Jan 26, 2011 at 4:09 PM, MinRK <<a href="mailto:benjaminrk@gmail.com">benjaminrk@gmail.com</a>><br>
>>>>>>> wrote:<br>
>>>>>>> >> What version of pyzmq do you have? If you are still using<br>
>>>>>>> 2.0.9,<br>
>>>>>>> then<br>
>>>>>>> >> that's before we made this addition (early October).<br>
>>>>>>> >> I realize that since IPython depends on 2.6, I can just import<br>
>>>>>>> the<br>
>>>>>>> (super<br>
>>>>>>> >> slow) builtin json module, rather than follow pyzmq's import<br>
>>>>>>> preferences.<br>
>>>>>>> >><br>
>>>>>>> >> -MinRK<br>
>>>>>>> >> On Wed, Jan 26, 2011 at 16:00, Brian Granger<br>
>>>>>>> <<a href="mailto:ellisonbg@gmail.com">ellisonbg@gmail.com</a>><br>
>>>>>>> wrote:<br>
>>>>>>> >>><br>
>>>>>>> >>> Fernando,<br>
>>>>>>> >>><br>
>>>>>>> >>> This is actually an import from pyzmq:<br>
>>>>>>> >>><br>
>>>>>>> >>> In [4]: from zmq.utils import jsonapi as json<br>
>>>>>>> >>><br>
>>>>>>> >>> In [5]: json.__file__<br>
>>>>>>> >>> Out[5]:<br>
>>>>>>> >>><br>
>>>>>>><br>
>>>>>>> '/Users/bgranger/Documents/Computation/zeromq/pyzmq/zmq/utils/jsonapi.pyc'<br>
>>>>>>> >>><br>
>>>>>>> >>> So it looks like something is odd with your pyzmq<br>
>>>>>>> install...unless<br>
>>>>>>> for<br>
>>>>>>> >>> some reason Python is putting the IPython directory in you<br>
>>>>>>> sys.path<br>
>>>>>>> >>> so importing zmq picks up IPython.zmq instead of zmq (pyzmq).<br>
>>>>>>> Can<br>
>>>>>>> you<br>
>>>>>>> >>> look at your pyzmq install?<br>
>>>>>>> >>><br>
>>>>>>> >>> Brian<br>
>>>>>>> >>><br>
>>>>>>> >>><br>
>>>>>>> >>> On Wed, Jan 26, 2011 at 3:31 PM, Fernando Perez<br>
>>>>>>> <<a href="http://fperez.net" target="_blank">fperez.net</a>@<a href="http://gmail.com" target="_blank">gmail.com</a>><br>
>>>>>>> >>> wrote:<br>
>>>>>>> >>> > Hey guys,<br>
>>>>>>> >>> ><br>
>>>>>>> >>> > as I was working on the 'asdf' bug I just posted about, I<br>
>>>>>>> tried<br>
>>>>>>> to use<br>
>>>>>>> >>> > the Qt console after updating my trunk, and got this:<br>
>>>>>>> >>> ><br>
>>>>>>> >>> > (trunk)dreamweaver[ipython]> ipython-qtconsole<br>
>>>>>>> >>> > Traceback (most recent call last):<br>
>>>>>>> >>> > File "/home/fperez/usr/bin/ipython-qtconsole", line 4, in<br>
>>>>>>> <module><br>
>>>>>>> >>> > from IPython.frontend.qt.console.ipythonqt import main<br>
>>>>>>> >>> > File<br>
>>>>>>> >>> ><br>
>>>>>>><br>
>>>>>>> "/home/fperez/ipython/ipython/IPython/frontend/qt/console/ipythonqt.py",<br>
>>>>>>> >>> > line 17, in <module><br>
>>>>>>> >>> > from IPython.frontend.qt.kernelmanager import<br>
>>>>>>> QtKernelManager<br>
>>>>>>> >>> > File<br>
>>>>>>> >>> ><br>
>>>>>>> "/home/fperez/ipython/ipython/IPython/frontend/qt/kernelmanager.py",<br>
>>>>>>> >>> > line 9, in <module><br>
>>>>>>> >>> > from IPython.zmq.kernelmanager import KernelManager,<br>
>>>>>>> >>> > SubSocketChannel, \<br>
>>>>>>> >>> > File<br>
>>>>>>> "/home/fperez/ipython/ipython/IPython/zmq/kernelmanager.py",<br>
>>>>>>> >>> > line 36, in <module><br>
>>>>>>> >>> > from session import Session, Message<br>
>>>>>>> >>> > File "/home/fperez/ipython/ipython/IPython/zmq/session.py",<br>
>>>>>>> line<br>
>>>>>>> 7,<br>
>>>>>>> >>> > in <module><br>
>>>>>>> >>> > from zmq.utils import jsonapi as json<br>
>>>>>>> >>> > ImportError: No module named utils<br>
>>>>>>> >>> ><br>
>>>>>>> >>> ><br>
>>>>>>> >>> > Not sure when it broke, but I suspect the merge of the recent<br>
>>>>>>> session<br>
>>>>>>> >>> > branch might have something to do with it.<br>
>>>>>>> >>> ><br>
>>>>>>> >>> > Brian/Min, do you guys have an idea of what happened, maybe<br>
>>>>>>> just<br>
>>>>>>> a<br>
>>>>>>> >>> > file someone forgot to add from their local working tree?<br>
>>>>>>> >>> ><br>
>>>>>>> >>> > Cheers,<br>
>>>>>>> >>> ><br>
>>>>>>> >>> > f<br>
>>>>>>> >>> > _______________________________________________<br>
>>>>>>> >>> > IPython-dev mailing list<br>
>>>>>>> >>> > <a href="mailto:IPython-dev@scipy.org">IPython-dev@scipy.org</a><br>
>>>>>>> >>> > <a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
>>>>>>> >>> ><br>
>>>>>>> >>><br>
>>>>>>> >>><br>
>>>>>>> >>><br>
>>>>>>> >>> --<br>
>>>>>>> >>> Brian E. Granger, Ph.D.<br>
>>>>>>> >>> Assistant Professor of Physics<br>
>>>>>>> >>> Cal Poly State University, San Luis Obispo<br>
>>>>>>> >>> <a href="mailto:bgranger@calpoly.edu">bgranger@calpoly.edu</a><br>
>>>>>>> >>> <a href="mailto:ellisonbg@gmail.com">ellisonbg@gmail.com</a><br>
>>>>>>> >>> _______________________________________________<br>
>>>>>>> >>> IPython-dev mailing list<br>
>>>>>>> >>> <a href="mailto:IPython-dev@scipy.org">IPython-dev@scipy.org</a><br>
>>>>>>> >>> <a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
>>>>>>> >><br>
>>>>>>> >><br>
>>>>>>> ><br>
>>>>>>> ><br>
>>>>>>> ><br>
>>>>>>> > --<br>
>>>>>>> > Brian E. Granger, Ph.D.<br>
>>>>>>> > Assistant Professor of Physics<br>
>>>>>>> > Cal Poly State University, San Luis Obispo<br>
>>>>>>> > <a href="mailto:bgranger@calpoly.edu">bgranger@calpoly.edu</a><br>
>>>>>>> > <a href="mailto:ellisonbg@gmail.com">ellisonbg@gmail.com</a><br>
>>>>>>> ><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> --<br>
>>>>>>><br>
>>>>>>> Brian E. Granger, Ph.D.<br>
>>>>>>> Assistant Professor of Physics<br>
>>>>>>> Cal Poly State University, San Luis Obispo<br>
>>>>>>> <a href="mailto:bgranger@calpoly.edu">bgranger@calpoly.edu</a><br>
>>>>>>> <a href="mailto:ellisonbg@gmail.com">ellisonbg@gmail.com</a><br>
>>>>>>><br>
>>>>>> _______________________________________________<br>
>>>>>> IPython-dev mailing list<br>
>>>>>> <a href="mailto:IPython-dev@scipy.org">IPython-dev@scipy.org</a><br>
>>>>>> <a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
>>>>><br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> IPython-dev mailing list<br>
>>>>> <a href="mailto:IPython-dev@scipy.org">IPython-dev@scipy.org</a><br>
>>>>> <a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
>>>>><br>
>>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> --<br>
>>>> Erik Tollerud<br>
>>>> _______________________________________________<br>
>>>> IPython-dev mailing list<br>
>>>> <a href="mailto:IPython-dev@scipy.org">IPython-dev@scipy.org</a><br>
>>>> <a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
>>>><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> Brian E. Granger, Ph.D.<br>
>>> Assistant Professor of Physics<br>
>>> Cal Poly State University, San Luis Obispo<br>
>>> <a href="mailto:bgranger@calpoly.edu">bgranger@calpoly.edu</a><br>
>>> <a href="mailto:ellisonbg@gmail.com">ellisonbg@gmail.com</a><br>
>><br>
>><br>
><br>
><br>
><br>
> --<br>
> Brian E. Granger, Ph.D.<br>
> Assistant Professor of Physics<br>
> Cal Poly State University, San Luis Obispo<br>
> <a href="mailto:bgranger@calpoly.edu">bgranger@calpoly.edu</a><br>
> <a href="mailto:ellisonbg@gmail.com">ellisonbg@gmail.com</a><br>
</div></div></blockquote></div><br></div></div>