PEP 639: Clarify License-File field, slim down terminology & remove future PEPs #2298
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CAM-Gerlach
force-pushed
the
pep-639-reduce-length-p1
branch
from
0b8e3c5 to
85b2648
Compare
AA-Turner
approved these changes
Feb 3, 2022
AA-Turner
approved these changes
Feb 3, 2022
|
(just realised I already "approved" this, I suppose approving a second time doesn't hurt!) |
|
Also, @brettcannon , if you still feel that |
|
@CAM-Gerlach let's worry about bikeshedding for another PR. 😉 |
|
FYI don't wait on my review to merge this and get the PEP to a state that you want me to review it. |
|
Done, thanks @brettcannon ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following @pfmoore and @brettcannon 's feedback, I've revised some of the
License-Filetext to state that it represents a record of the license file relative paths in the project source tree, and in the PyPA-specified distribution and installed projects formats to the file paths relative to the defined license root directory, with its meaning in unspecified legacy, new and non-standard distribution, installation and metadata formats defined by the needs of the particular format. I've also clarified a bit of terminology elsewhere.Also, as another incremental step toward reducing the length of the PEP, I've eliminated the superfluous "Future PEPs" section, since none of those speculated PEPs are directly germane to this one, and also greatly slimmed down the terminology section, particularly the introductory material and from the PyPA PyPUG glossary. This cuts out around a page of the PEP's total length. I've also moved the User Scenarios section to an appendix, reducing the main PEP length by 2 more pages, and de-numbered the existing appendices. If and when PEP-0676 is accepted, all of the appendices, along with all the rejected ideas but a summary of the most important, will be moved to separate linked documents in the PEP repo, reducing the main PEP's length by a further nearly 2/3rds and the ToC by over 3/4. The Open Issues will also be eliminated once closed.