-
Notifications
You must be signed in to change notification settings - Fork 134
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
Support [project] table in pyproject.toml (PEP 621) #393
Merged
Changes from 1 commit
Commits
Show all changes
28 commits
Select commit
Hold shift click to select a range
ce2ec0d
Start integrating support for PEP 621 metadata
takluyver 62c26e7
Remove f-strings :(
takluyver 6755cd0
Validate that dynamic fields are listed
takluyver b1a170d
Test loading config for PEP 621 with no dynamic fields
takluyver 7bebd01
Set module name from PEP 621 table
takluyver 6110be5
Remove unused metadata_and_module_from_ini_path function
takluyver 432dc76
Avoid reusing imported modules for getting metadata
takluyver bd43136
Only get dynamic fields from module contents
takluyver d8e9c0a
Remove debugging prints
takluyver 02e364c
Some integration tests for PEP 621 metadata
takluyver 6472383
No extra build requirements with statically specified metadata
takluyver 06352f1
Remove stray f-string
takluyver 449a687
Test author metadata from [project] table
takluyver 87cac59
Don't modify dict when creating Metadata object
takluyver f1090e4
Fix error message
takluyver bea8d33
Fix starting 'flit install' with statically specified PEP 621 metadata
takluyver 2d6fd33
Fix [build-system] tables for PEP 621 samples
takluyver 91394d5
Version number -> 3.2.0
takluyver d3043ff
Normalise version number coming from PEP 621 config
takluyver 77eb453
Exercise reading more PEP 621 fields
takluyver 059a130
Correct scripts & gui-scripts tables
takluyver 85b1684
Add keywords & classifiers to PEP 621 samples
takluyver e781ed7
Add requires-python field to PEP 621 sample
takluyver 97e9918
Test error checking in PEP 621 [project] table
takluyver c5134d6
Test checking for relative path to README
takluyver 88dde16
Test unrecognised field in project.readme table
takluyver 43b7c54
Use email.headerregistry.Address to format 'name <email@domain>'
takluyver 746afdc
Allow module name != distribution name with PEP 621
takluyver File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Remove f-strings :(
- Loading branch information
commit 62c26e78bad470da05004e82ee4a8d86f88ff0a9
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Users can include weird stuff in this field and break the formatting. Not sure if this is an issue.
{ name = "Jane\n\n\nDoe <[email protected]>", email="[email protected]" }
One could use
formataddr
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I didn't know about that function. It somewhat garbles non-ASCII text, though:
I don't know if that's what should happen. The original version metadata spec 1.0 (PEP 241) says the format is based on email headers, and presumably that's what email headers do. But that was almost 20 years ago, and it's possible that tools expect something a bit more Unicode native now. PEP 621 explicitly suggests "the format
{name} <{email}>
".I'll open a discussion on the Python discourse about this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://discuss.python.org/t/core-metadata-email-fields-unicode/7421