publish a new (redirecting) allmydata-tahoe to PyPI #2764

Open
opened 2016-04-01 16:44:41 +00:00 by warner · 2 comments
warner commented 2016-04-01 16:44:41 +00:00
Owner

Now that tahoe-lafs-1.11.0 is on PyPI and is pip-installable, we should maybe do something about the old allmydata-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 did pip install allmydata-tahoe, or who had it installed and did a pip install --upgrade allmydata-tahoe, would wind up with both, but only tahoe-lafs would provide the tahoe 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 or allmydata-tahoe will both get them a modern tahoe executable. Without it, picking the wrong one will get you weird zetuptoolz errors at best, and an older version of tahoe at worst.

Now that `tahoe-lafs-1.11.0` is on PyPI and is pip-installable, we should maybe do something about the old `allmydata-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](https://pypi.python.org/pypi/pypi-alias), that would depend upon `tahoe-lafs` but is otherwise empty. Anyone who accidentally did `pip install allmydata-tahoe`, or who had it installed and did a `pip install --upgrade allmydata-tahoe`, would wind up with both, but only `tahoe-lafs` would provide the `tahoe` 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` or `allmydata-tahoe` will both get them a modern `tahoe` executable. Without it, picking the wrong one will get you weird zetuptoolz errors at best, and an older version of `tahoe` at worst.
tahoe-lafs added the
dev-infrastructure
normal
task
1.11.0
labels 2016-04-01 16:44:41 +00:00
tahoe-lafs added this to the soon (release n/a) milestone 2016-04-01 16:44:41 +00:00
daira commented 2016-04-04 20:25:29 +00:00
Author
Owner

+1 for using pypi-alias. (We should review what it produces, though.)

+1 for using pypi-alias. (We should review what it produces, though.)
meejah commented 2021-03-30 18:41:12 +00:00
Author
Owner

Ticket retargeted after milestone closed

Ticket retargeted after milestone closed
tahoe-lafs modified the milestone from soon (release n/a) to soon 2021-03-30 18:41:12 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#2764
No description provided.