Skip to content

PEP 1: Update some out of date details #576

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

Merged
merged 1 commit into from
Apr 21, 2018

Conversation

ncoghlan
Copy link
Contributor

  • some interoperability specifications (e.g. the package index
    download API) will never have a standard library implementation
  • auxiliary files can go in a subdirectory
  • PEP issues should be reported against the GitHub repo rather than
    bugs.python.org

- some interoperability specifications (e.g. the package index
  download API) will never have a standard library implementation
- auxiliary files can go in a subdirectory
- PEP issues should be reported against the GitHub repo rather than
  bugs.python.org
@ncoghlan
Copy link
Contributor Author

I'm finally working on a PR for #270, and noticed some out of date details in PEP 1 that I decided were better submitted as their own separate PR (this is also how I noticed #575)

@ncoghlan ncoghlan merged commit a60ad15 into python:master Apr 21, 2018
@ncoghlan
Copy link
Contributor Author

@warsaw @gvanrossum I went ahead and merged this cleanup, since it seemed better to do that rather than leaving the inaccurate info in the PEP.

@warsaw
Copy link
Member

warsaw commented Apr 21, 2018

Thanks @ncoghlan !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants