publish a new (redirecting) allmydata-tahoe
to PyPI #2764
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
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2764
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Now that
tahoe-lafs-1.11.0
is on PyPI and is pip-installable, we should maybe do something about the oldallmydata-tahoe-1.10.2
that's on PyPI (and not really pip-installable).I was thinking we could publish a "1.10.2.post1" sort of thing, using pypi-alias, that would depend upon
tahoe-lafs
but is otherwise empty. Anyone who accidentally didpip install allmydata-tahoe
, or who had it installed and did apip install --upgrade allmydata-tahoe
, would wind up with both, but onlytahoe-lafs
would provide thetahoe
executable.With or without this, there will be confusion when people search for "tahoe" on PyPI, since they'll see both packages (in fact there's a completely unrelated
tahoe
package up there, described as "A Flask-based framework that handles the tedious things", and at least one developer tried to install it by mistake).But with this, installing
tahoe-lafs
orallmydata-tahoe
will both get them a moderntahoe
executable. Without it, picking the wrong one will get you weird zetuptoolz errors at best, and an older version oftahoe
at worst.+1 for using pypi-alias. (We should review what it produces, though.)
Ticket retargeted after milestone closed