<br><br><div class="gmail_quote"><div dir="ltr">Le mer. 27 janv. 2016 01:18, Craig Treleaven <<a href="mailto:ctreleaven@cogeco.ca">ctreleaven@cogeco.ca</a>> a écrit :<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">Thanks, I’ll keep an eye out for the release.<div><br></div><div>BTW, will 0.9 ‘workers’ be compatible with 0.8.x masters?</div></div><div style="word-wrap:break-word"><div></div></div></blockquote></div><div><br></div><div>Unfortunately this is not a goal. The package name will be different so you can install 0.8 and 0.9 version in the same environment</div><div><br></div><div><br></div><div class="gmail_quote"><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>Craig</div></div><div style="word-wrap:break-word"><div><br><div><blockquote type="cite"></blockquote></div></div><div><blockquote type="cite"><div>On Jan 26, 2016, at 5:42 PM, Pierre Tardy <<a href="mailto:tardyp@gmail.com" target="_blank">tardyp@gmail.com</a>> wrote:</div><br><div><div dir="ltr">I just tried to upgrade and look at the tests, and created a report in the following trac:<div><br></div><div><a href="http://trac.buildbot.net/ticket/3425#ticket" target="_blank">http://trac.buildbot.net/ticket/3425#ticket</a><br></div><div><br></div><div>I dont think it should be so hard to fix</div></div><br><div class="gmail_quote"><div dir="ltr">Le mar. 26 janv. 2016 à 23:28, Pierre Tardy <<a href="mailto:tardyp@gmail.com" target="_blank">tardyp@gmail.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div dir="ltr">Le mar. 26 janv. 2016 à 21:49, Craig Treleaven <<a href="mailto:ctreleaven@cogeco.ca" target="_blank">ctreleaven@cogeco.ca</a>> a écrit :<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>Just to be clear, two of us from the MacPorts project have said that we want to fix our port. It appears that a fork of sqlalchemy-migrate has emerged that (presumably) works with current versions of sqlalchemy. (With Python 3 support, I believe.) </div></div></blockquote><div><br></div></div></div><div dir="ltr"><div class="gmail_quote"><div>I Craig, I did not realize you were part of the macport team, and didn't want to be rude.</div></div></div><div dir="ltr"><div class="gmail_quote"><div> </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>Surely the Buildbot project would want to move forward with a module that is being supported rather than stick with an old version? If that fork is incompatible with Buildbot, perhaps there is another, better version?</div></div></blockquote></div></div><div dir="ltr"><div class="gmail_quote"><div>It is very hard for us to keep up with the evolution of all our dependencies, we get more or less 1 regression every other month because a dependency incompatible change.</div><div>We try to change our code in order to be compatible, but sometimes it looks like too much work so we just lazily add a rule in our setup.py to enforce that this or that dependency is fixed to a particular version.</div><div><br></div><div>Looking at setup.py only the following package have restrictions:</div><div><div> 'sqlalchemy >= 0.6, <= 0.7.10',</div><div> 'sqlalchemy-migrate==0.7.2',</div></div><div><div> 'pylint==1.1.0',</div></div><div><br></div><div>We know that this is not very cool for our distro package maintainers, but as virtualenv is so easy to use, and resolves the python dependency hell so well for us, its hard for us to find the motivation to resolve those bugs.</div></div></div><div dir="ltr"><div class="gmail_quote"><div><br></div><div><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>I’m not a Python guy—I’ve essentially gone down the rabbit hole trying to set up an OS X builder for MythTV. </div></div></blockquote><div><br></div></div></div><div dir="ltr"><div class="gmail_quote"><div>If this is only that, you can safely install a buildbot "slave" (will soon be renamed as "worker") package only, which has much less dependencies.</div></div></div><div dir="ltr"><div class="gmail_quote"><div> </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>‘virtualenv’ is just another layer between me and the problem that I’d rather be solving. It looks like I’m going to go that way for the sake of testing my build-slave but I do want to fix our buildbot port.</div></div></blockquote><div><br></div></div></div><div dir="ltr"><div class="gmail_quote"><div>I am not exactly sure how hard it will be to fix buildbot to release the restriction on sqlalchemy, as this is the db part, everybody is a little bit scary touching that.</div><div><br></div><div><br></div></div></div></blockquote></div>
</div></blockquote></div><br></div></blockquote></div>