pip
managed install is broken.
#2032
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2032
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Synopsis:
The command
pip install allmydata-tahoe
fails because of a bug in theNevow
dependency.Known workaround:
Install
twisted
first with pip. This works for me:Details:
It appears related to
Nevow
. I'm hopping on#twisted
to ask for advice.This is a known
Nevow
vspip
issue: https://bugs.launchpad.net/nevow/+bug/1091055I've submitted a patch to Nevow which fixes this issue (at least on my system): https://bugs.launchpad.net/nevow/+bug/1091055/comments/5
I consider this major because I'm part of the PyPI + pip hegemony which intends to take over the (python) world. Also, check out this claim of >40,000 PyPI downloads!
See also #1963
"replace nevow with twisted.web.template"
Replying to nejucomo:
Also, to keep the ball rolling I attempted to translate the patch into a bzr / lp merge request.
I believe that, due to this Nevow commit, the bug only happens when
import setuptools
fails (as it will in a clean virtualenv).... and Zooko correctly anticipated the problem two years ago. How annoying.
[12:28] <dstufft>
setuptools should always be importable when you're installing with pip (unless you hit the pip bug that uninstalls setuptools but your entire install will break then)[12:31] <dstufft>
daira1: pip is still broken with Nevow because the last release of Nevow was made in 2009 and it does not contain that commit[12:32] <daira1>
wow. okayReplying to daira:
There may be more than one bug. I don't understand what the presence of
setuptools
has to do with the bug I find when runningpip install nevow
, which is that ifsetup.py
importsnevow
, then it will importtwisted
.If
twisted
is not installed, thensetup.py
will raise anImportError
. This prevents a user from running "python ./setup.py " unless they've already installed a dependency. If this is true then I believe it would also breakeasy_install
or any other case wheresetup.py
is executed prior to satisfying dependencies.Replying to [nejucomo]comment:13:
I was mistaken: the Nevow commit isn't in any release yet [isn't on trunk, since the branch was never merged]and. pip depends on setuptools so that will always be present.
I've added a comment on https://bugs.launchpad.net/nevow/+bug/812537 saying that this issue is causing Tahoe-LAFS users to be unable to install it.
Nevow-0.11.1 was released a few days ago (https://github.com/twisted/nevow/blob/nevow-0.11.1/NEWS.txt), and supports install from 'pip'. I just confirmed that a simple
pip install allmydata-tahoe
in a clean virtualenv gets me a workingtahoe
binary (andtahoe debug repl
canimport nevow
without complaint).Closing this one out. Yay! Crediting this to the 1.11 milestone (even though it was fixed by something outside of tahoe's source tree) so we remember to mention it in the release notes.
Daira and I noticed we do not yet depend on
Nevow >= 0.11.1
. We're not yet sure if it's still possible to run into this problem, but it might be prudent to bump the requirement up.I'm going to reopen this to ensure we bump the dependency version or discuss why not to do so.
Replying to nejucomo:
Moved to #2291. The original problem is fixed just by the availability of Nevow 0.11.1.