<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body dir="auto">
<div style="-webkit-text-size-adjust: auto;">So taskflow was tested with the version of sqlalchemy that was available and in the requirements at the time of its 0.1 release (taskflow syncs it's requirements from the same global requirements). From what I remember
this is the same requirement that everyone else is bound to: </div>
<div>
<pre style="box-sizing: border-box; word-wrap: normal; margin-top: 0px; margin-bottom: 0px; overflow: scroll; padding: 15px 0px;"><div class="line" id="LC8" style="box-sizing: border-box; padding: 0px 15px;"><font face="UICTFontTextStyleBody"><span style="white-space: normal; -webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">SQLAlchemy>=0.7.8,<=0.7.99</span></font></div></pre>
<span style="-webkit-text-size-adjust: auto;">
<div><span style="-webkit-text-size-adjust: auto;">I can unpin it if this is desired (the openstack requirements repo has the same version restriction). What would be recommended here? As more code moves to pypi reusable libraries (oslo.db when it arrives comes
to mind) I think this will be hit more often. Let's come up with a good strategy to follow.</span></div>
<div><span style="-webkit-text-size-adjust: auto;"><br>
</span></div>
<div><span style="-webkit-text-size-adjust: auto;">Thoughts?? </span></div>
<div><span style="-webkit-text-size-adjust: auto;"><br>
</span></div>
Sent from my really tiny device...</span></div>
<div style="-webkit-text-size-adjust: auto;"><br>
On Jan 3, 2014, at 7:30 AM, "Sean Dague" <<a href="mailto:sean@dague.net">sean@dague.net</a>> wrote:<br>
<br>
</div>
<blockquote type="cite" style="-webkit-text-size-adjust: auto;">
<div><span>Given that sqla 0.9 just came out, I wanted to explore, again, what the state of the world was with sqla 0.8 (especially given that Ubuntu and Red Hat are both shipping 0.8 in their OpenStack bundles) -
<a href="https://review.openstack.org/#/c/64831/">https://review.openstack.org/#/c/64831/</a></span><br>
<span></span><br>
<span>The answer is not great. But more importantly, the answer is actually worse than the last time we checked, which I think gives this some urgency to move forward.</span><br>
<span></span><br>
<span>One of the key problems is taskflow, which has an sqla pin, which breaks all the cinder entry points. This was actually entirely the problem global requirements was meant to address, but it really can't when there are nested requirements like this, in
stackforge projects that aren't installing via git (so we can rewrite their requirements).</span><br>
<span></span><br>
<span>So why does taskflow have the SQLA pin? And if the answer is global requirements, then taskflow can't be installing via pypi like it is now, because it's by nature taking a wedge. So we need a real solution here to un bind us, because right now it's actually
impossible to upgrade sqla in requirements because of taskflow.</span><br>
<span></span><br>
<span> -Sean</span><br>
<span></span><br>
<span>-- </span><br>
<span>Sean Dague</span><br>
<span>Samsung Research America</span><br>
<span><a href="mailto:sean@dague.net">sean@dague.net</a> / <a href="mailto:sean.dague@samsung.com">
sean.dague@samsung.com</a></span><br>
<span><a href="http://dague.net">http://dague.net</a></span><br>
<span></span><br>
<span>_______________________________________________</span><br>
<span>OpenStack-dev mailing list</span><br>
<span><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a></span><br>
<span><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></span><br>
</div>
</blockquote>
</body>
</html>