-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
Structure for importlib metadata identities #108580
Comments
Add `PackageMetadata.authors` and `PackageMetadata.maintainers` to the `importlib.metadata` module. These unify and provide minimal parsing for the respective core metadata fields ("Author", "Author-email"), and ("Maintainer", "Maintainer-email").
Correct the parsing of name/email entries in the 'Author-email' and 'Maintainer-email' fields of the core metadata specification.
Add `PackageMetadata.authors` and `PackageMetadata.maintainers` to the `importlib.metadata` module. These unify and provide minimal parsing for the respective core metadata fields ("Author", "Author-email"), and ("Maintainer", "Maintainer-email").
Correct the parsing of name/email entries in the 'Author-email' and 'Maintainer-email' fields of the core metadata specification.
A hypothesis strategy for generating structured core metadata and equivalent unstructured text. Ensures that parsing the text using PackageMetadata results in the same structure - a roundtrip test.
A hypothesis strategy for generating structured core metadata and equivalent unstructured text. Ensures that parsing the text using PackageMetadata results in the same structure - a roundtrip test.
A `note` stub which does nothing.
Correct the generation of identity entries in the core metadata specification.
Correct the parsing of name/email entries using feedback from the hypothesis test.
Add `PackageMetadata.authors` and `PackageMetadata.maintainers` to the `importlib.metadata` module. These unify and provide minimal parsing for the respective core metadata fields ("Author", "Author-email"), and ("Maintainer", "Maintainer-email").
Correct the parsing of name/email entries in the 'Author-email' and 'Maintainer-email' fields of the core metadata specification.
A hypothesis strategy for generating structured core metadata and equivalent unstructured text. Ensures that parsing the text using PackageMetadata results in the same structure - a roundtrip test.
A `note` stub which does nothing.
Correct the generation of identity entries in the core metadata specification.
Correct the parsing of name/email entries using feedback from the hypothesis test.
(for posterity, at the time of writing, the discuss.python.org post has received no responses from anyone other than OP) |
Status update, the PRs in #108585 and python/importlib_metadata#471 have stalled out after hitting some crucial issues. I personally am using some rudimentary routines in jaraco.packaging.metadata for similar purposes (and others are welcome to do so as well) until something more robust is accepted into importlib metadata. |
I'd still like to see something on this, though I'm unlikely to get to an implementation any time soon. If anyone else is interested in this issue, please see the linked PRs and the challenges with those proposed changes and consider proposing a refinement that addresses the identified concerns. |
Feature or enhancement
Has this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
Structure for importlib metadata identities
Proposal:
See the linked discussion for the proposal, justification, conflicts, and examples.
Linked PRs
The text was updated successfully, but these errors were encountered: