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.

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

Revise legacy upload error message #2176

Merged
merged 4 commits into from
Jul 10, 2017
Merged

Revise legacy upload error message #2176

merged 4 commits into from
Jul 10, 2017

Conversation

ddbeck
Copy link
Contributor

@ddbeck ddbeck commented Jul 9, 2017

As evidenced by pypa/packaging.python.org#346, uploading a file is not so "simple." I've tried to change the message to be a little more direct about what to do instead.

@ncoghlan
Copy link
Contributor

ncoghlan commented Jul 9, 2017

The new section I just added to the migration guide about this change may be a better reference: https://packaging.python.org/guides/migrating-to-pypi-org/#registering-package-names-metadata

@ncoghlan
Copy link
Contributor

ncoghlan commented Jul 9, 2017

As far as a revised error message goes, I think the main problem here is the reference to "This API", which may be thoroughly ambiguous when displayed by a client. Here's a possibly clearer alternative:

Project pre-registration is no longer required or supported, so please continue directly to uploading files.

I'm less sure about including a link given that more precise wording, though - I've changed the migration page to actually quote the error message (so search engines should figure it out as long as we keep the messages in sync), and we really don't have much more to say about the matter than what's in that message (short of referring people off to the gory details in #1627, and I'm not sure we want to do that)

@dstufft dstufft merged commit 57f70e9 into pypi:master Jul 10, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants