Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

notice obsolete repository settings and warn user more usefully #307

Closed
brainwane opened this issue Mar 1, 2018 · 0 comments
Closed

notice obsolete repository settings and warn user more usefully #307

brainwane opened this issue Mar 1, 2018 · 0 comments
Labels
enhancement

Comments

@brainwane
Copy link
Contributor

Following up on @tdicola's and others' comments in #200 (comment) , #270, #258, here's a feature request:

If Twine notices that it's getting an obsolete repository setting (in particular https://pypi.python.org/pypi) from a [repository] flag in .pypirc,

It would be really, really nice for twine to catch this case and give an actionable error since previous packaging instructions told people to add that repository line, etc.
@brainwane brainwane mentioned this issue Mar 1, 2018
Closed
brainwane added a commit that referenced this issue Mar 18, 2018
@brainwane
Raise exception if attempting upload to deprecated legacy PyPI URLs
c567730 
Now that legacy (deprecated) URLs give a 410 Gone,
Twine should just watch for those URLs and give
an actionable error rather than transmit the upload
request.

Fixes #307.
@brainwane brainwane mentioned this issue Mar 18, 2018
Merged
brainwane added a commit that referenced this issue Mar 18, 2018
@brainwane
Raise exception if attempting upload to deprecated legacy PyPI URLs
7e45d27 
Now that legacy (deprecated) URLs give a 410 Gone,
Twine should just watch for those URLs and give
an actionable error rather than transmit the upload
request.

Fixes #307.
brainwane added a commit that referenced this issue Mar 18, 2018
@brainwane
Raise exception attempting upload to deprecated PyPI URLs
9c2fda1 
Now that legacy (deprecated) URLs give a 410 Gone,
Twine should just watch for those URLs and give
an actionable error rather than transmit the upload
request.

Fixes #307.
brainwane added a commit that referenced this issue Mar 18, 2018
@brainwane
Raise exception attempting upload to deprecated PyPI URLs
6790de5 
Now that legacy (deprecated) URLs give a 410 Gone,
Twine should just watch for those URLs and give
an actionable error rather than transmit the upload
request.

Fixes #307.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brainwane