I have updated cliff with a patch to peg the version of PyParsing that I based on the (unreleased?) cmd2 change that does the same thing [1]. I've also contacted the cmd2 author to see about a formal release with that fix.<div>
<br></div><div>Try with cliff 1.3.1, and if that doesn't fix the problem try setting the pyparsing version requirement in tools/pip-requires to 1.5.7.</div><div><br></div><div>Doug<br><div><div><br><div class="gmail_quote">
On Wed, Feb 27, 2013 at 7:39 AM, gong yong sheng <span dir="ltr"><<a href="mailto:gongysh@linux.vnet.ibm.com" target="_blank">gongysh@linux.vnet.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>pyparsing 2.0 is installed because of
the pip-requrires of python-quantumclient at
<a href="https://pypi.python.org/packages/source/p/python-quantumclient/python-quantumclient-2.1.tar.gz#md5=0fcdf72512ef3a056e95de2a95457702" target="_blank">https://pypi.python.org/packages/source/p/python-quantumclient/python-quantumclient-2.1.tar.gz#md5=0fcdf72512ef3a056e95de2a95457702</a>:<br>
cliff>=1.2.1<br>
argparse<br>
httplib2<br>
prettytable>=0.6.0<br>
simplejson<br>
pyparsing<br>
<br>
It is not limiting the version number of pyparsing.<div><div class="h5"><br>
<br>
On 02/27/2013 08:29 PM, Kieran Spear wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div class="gmail_quote">On 27 February 2013 19:52, Mark McClain <span dir="ltr"><<a href="mailto:mark.mcclain@dreamhost.com" target="_blank">mark.mcclain@dreamhost.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Kieran-
<div><br>
</div>
<div>I've been looking into this issue. We tried building a
package that corrects the dependency problem, but the
issue is upstream of the python-quantumclient. cmd2
installs the wrong version before the Quantum client's
dependencies are evaluated.</div>
</div>
</blockquote>
<div><br>
Poking around in a 2.0 checkout, it looks like pip-requires
isn't being used anywhere? It's not referenced in setup.py or
tox.ini. Is this intentional?<br>
<br>
Cheers,<br>
Kieran<br>
<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div>
<div><br>
</div>
<div>mark</div>
<div><br>
<div>
<div>
<div>
<div>On Feb 27, 2013, at 2:40 AM, Kieran Spear
<<a href="mailto:kispear@gmail.com" target="_blank">kispear@gmail.com</a>>
wrote:</div>
<br>
</div>
</div>
<blockquote type="cite">
<div>
<div>It must be a day for breaking
releases. pyparsing 2.0 was just uploaded to
pypi and is not compatible with python 2.x.<br>
Quantumclient is pulling it in.<br>
<br>
See:<br>
<br>
<a href="https://review.openstack.org/#/c/22295/" target="_blank">https://review.openstack.org/#/c/22295/</a><br>
<a href="http://logs.openstack.org/22295/2/gate/gate-horizon-python26/1655/console.html" target="_blank">http://logs.openstack.org/22295/2/gate/gate-horizon-python26/1655/console.html</a><br>
<br>
quantumclient has been fixed to pin pyparsing
[1], but the commit hasn't made it into a pypi
release yet.<br>
Do we need a 2.1.1 release of quantumclient?<br>
<br>
Cheers,<br>
Kieran<br>
<br>
</div>
</div>
[1] <a href="https://bugs.launchpad.net/python-quantumclient/+bug/1091028" target="_blank">https://bugs.launchpad.net/python-quantumclient/+bug/1091028</a>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div></div>