txi2p dependency declared wrong #3608

Closed
opened 2021-02-07 17:37:18 +00:00 by meejah · 1 comment
Owner

The way we've declared the txi2p dependency makes PyPI sad when trying to upload the resulting wheel. An error like this:

HTTPError: 400 Client Error: Invalid value for requires_dist. Error: Can't have direct dependency: "txi2p @ git+https://github.com/str4d/txi2p@0611b9a86172cb70d2f5e415a88eee9f230590b3#egg=txi2p ; extra == 'i2p'" for url: https://test.pypi.org/legacy/

The test.pypi.org instance also produces the error, but installing locally (or using twine check) does not show any error. I am not sure what the correct way to declare this dependency is (such that PyPI will accept it).

The way we've declared the txi2p dependency makes PyPI sad when trying to upload the resulting wheel. An error like this: ``` HTTPError: 400 Client Error: Invalid value for requires_dist. Error: Can't have direct dependency: "txi2p @ git+https://github.com/str4d/txi2p@0611b9a86172cb70d2f5e415a88eee9f230590b3#egg=txi2p ; extra == 'i2p'" for url: https://test.pypi.org/legacy/ ``` The test.pypi.org instance also produces the error, but installing locally (or using `twine check`) does not show any error. I am not sure what the correct way to declare this dependency is (such that PyPI will accept it).
meejah added the
code
critical
defect
n/a
labels 2021-02-07 17:37:18 +00:00
meejah added this to the 1.15.0 milestone 2021-02-07 17:37:18 +00:00
GitHub <noreply@github.com> commented 2021-03-02 13:14:08 +00:00
Owner

In f5aec97/trunk:

Merge pull request #993 from LeastAuthority/3608.txi2p-dependency.2

Back off from the master revision txi2p dependency

Fixes: ticket:3608
In [f5aec97/trunk](/tahoe-lafs/trac-2024-07-25/commit/f5aec9701d2137b603b4fb08ac93899c6f77db8a): ``` Merge pull request #993 from LeastAuthority/3608.txi2p-dependency.2 Back off from the master revision txi2p dependency Fixes: ticket:3608 ```
tahoe-lafs added the
fixed
label 2021-03-02 13:14:08 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

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