[tahoe-lafs-trac-stream] [tahoe-lafs] #1274: eliminate pywin32 dependency
tahoe-lafs
trac at tahoe-lafs.org
Mon Jun 13 22:30:45 PDT 2011
#1274: eliminate pywin32 dependency
-------------------------+-------------------------------------------------
Reporter: | Owner: warner
davidsarah | Status: reopened
Type: defect | Milestone: 1.9.0
Priority: major | Version: 1.8.0
Component: code- | Keywords: pywin32 windows win64 install
storage | twisted review-needed
Resolution: |
Launchpad Bug: |
-------------------------+-------------------------------------------------
Changes (by zooko):
* cc: warner (added)
Comment:
Replying to [comment:32 davidsarah]:
>
> I have to say, I don't really understand what the problem is with having
a Tahoe instance built by '{{{python setup.py build}}}' use a local
instance of Twisted, when the installed instance is < 9.0.0.
Yeah, I guess the cost really isn't that bad. Also, while I feel a sort of
vague warm happiness about our longstanding compatibility with {{{Twisted
2.4.0}}}, it isn't really tested. A glance at [http://tahoe-
lafs.org/buildbot/waterfall our buildbot waterfall] shows the following
versions of Twisted: {{{8.1.0}}}, {{{10.1.0}}}, {{{11.0.0}}}, and
{{{10.0.0}}}. So claiming that Tahoe-LAFS works correctly with {{{Twisted
2.4.0}}} is best understood as "good intentions".
(Aside: I'm glad Brian hasn't yet gotten around to removing some of the
tool versions information from the waterfall, so that I was able to gather
that information by scanning a single page.)
The two {{{Twisted 8.1.0}}} buildslaves are both Debian 5 "Lenny". As you
say, if we raise this requirement then the Tahoe-LAFS build on those
buildslaves should just use a local copy of a newer version of Twisted.
Shall we try it?
I'd still like to hear from Brian on this ticket!
--
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1274#comment:34>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list