[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2221: allow automatic use of pyOpenSSL 0.14
Tahoe-LAFS
trac at tahoe-lafs.org
Mon May 4 23:13:07 UTC 2015
#2221: allow automatic use of pyOpenSSL 0.14
-------------------------+-------------------------------------------------
Reporter: daira | Owner:
Type: defect | Status: new
Priority: major | Milestone: soon
Component: | Version: 1.10.0
packaging | Keywords: packaging setuptools pyopenssl
Resolution: | cryptography six cffi pycparser
Launchpad Bug: |
-------------------------+-------------------------------------------------
Comment (by glyph):
Replying to [comment:11 zooko]:
> Replying to [comment:10 glyph]:
> > It seems like eliminating zetuptoolz would be a fruitful avenue to
pursue; why are you still stuck with it?
>
> Last time I considered it, which was [comment:4:ticket:2044 one and a
half years ago], we had made seven patches to our fork, zetuptoolz, and I
wasn't sure if those issues had also been fixed in setuptools or not.
Nowadays I guess I would be unsure if those issues would regress if we
switched from zetuptoolz to `wheel`…
My understanding is that the context of those patches was a fairly
unresponsive setuptools development team who wasn't fixing things. The
Python Packaging Authority is ''substantially'' more responsive to bug
reports, and users frequently get updates. Ironically `zetuptoolz` is now
creating the exact situation it was created to avoid :-).
The only setuptools bug referenced by the linked comment is
http://bugs.python.org/setuptools/issue54, which, if it hasn't been fixed
(I think maybe it has? maybe dstufft can opine directly) has been mostly
obviated by the ecosystem's consensus converging on virtualenv and related
toolchains to produce isolated environments.
I want to say more things about this but I can't even find zetuptoolz's
source code; all the old links are broken. Where does it live now?
--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2221#comment:13>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage
More information about the tahoe-lafs-trac-stream
mailing list