Skip to content

Conversation

@jwodder
Copy link
Contributor

@jwodder jwodder commented Jun 18, 2017

Rather than referring readers to a PEP via a link that doesn't even go to the right part of the page, this patch incorporates the salient points on project names from PEPs 426 and 503 into the section on the name argument to the setup() function.

Copy link
Member

@ncoghlan ncoghlan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I think this is definitely a useful improvement.

The reference to the still-in-Draft-form PEP 426 is actually outdated now, so it would make sense to update it before merging this.

characters, see the :pep:`name <426#name>`
section from :pep:`426`.
This is the name of your project, determining how your project is listed on
:term:`PyPI <Python Package Index (PyPI)>`. Per :pep:`426`, valid project
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be updated to refer to the accepted PEP 508 now: https://www.python.org/dev/peps/pep-0508/#names

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

@ncoghlan ncoghlan merged commit 14580ab into pypa:master Jun 18, 2017
@ncoghlan
Copy link
Member

Thanks!

ncoghlan pushed a commit to ncoghlan/packaging.python.org that referenced this pull request Jun 24, 2017
Als updates reference to be to PEP 508 instead of 426
@jwodder jwodder deleted the names branch June 26, 2017 00:50
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.

2 participants