Skip to content

Conversation

@pfmoore
Copy link
Member

@pfmoore pfmoore commented Jul 19, 2023

@python/pep-editors - I've grabbed the next PEP number (722) that seemed available. Hope that's OK, I can change the number if needed.


📚 Documentation preview 📚: https://pep-previews--3210.org.readthedocs.build/

@pfmoore pfmoore requested a review from a team as a code owner July 19, 2023 12:08
@AA-Turner AA-Turner added the new-pep A new draft PEP submitted for initial review label Jul 19, 2023
Copy link
Member

@hugovk hugovk left a comment

Choose a reason for hiding this comment

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

@pfmoore
Copy link
Member Author

pfmoore commented Jul 20, 2023

Just a quick note - thanks for the reviews, I'll address them once the first round of discussion on the PEP has died down a bit, as I expect there to be further changes coming from that.

@reece

This comment was marked as off-topic.

@merwok

This comment was marked as resolved.

@pfmoore
Copy link
Member Author

pfmoore commented Aug 3, 2023

OK, this has been updated following review comments here and discussion on Discourse. I plan on merging this so we have an "official" copy of the PEP under discussion, but I'll leave the merge for a little while in case anyone has a chance to review for typos, or similar, as it's a pretty major rewrite.

Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
Copy link
Member

@AA-Turner AA-Turner left a comment

Choose a reason for hiding this comment

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

I'll apply the two syntax changes such that the document renders properly. Otherwise, one question and some editorial suggestions.

A

@pfmoore pfmoore merged commit 69c3a96 into python:main Aug 3, 2023
@pfmoore pfmoore deleted the pep-722 branch August 3, 2023 21:14
the identifying characters ``##``. Whitespace is not allowed before the
identifying ``##``. More than one metadata block may exist in a Python file.

Tools reading dependency blocks MAY respect the standard Python encoding
Copy link

Choose a reason for hiding this comment

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

At this point of the "Specification" section we have only talked about metadata blocks, and script dependencies have not been introduced yet. So maybe it should read "Tools reading metadata blocks [...]" instead?

@pfmoore pfmoore mentioned this pull request Aug 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-pep A new draft PEP submitted for initial review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants