-
Notifications
You must be signed in to change notification settings - Fork 990
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
Possible to support displaying all authors
on PyPI page?
#12877
Labels
Comments
Is this a duplicate of #9400? |
Hm I think so. I'll assume yes and close here in favor of it, but actually check when I'm out of my next meeting. Apologies for the noise: I searched "authors" in the Issues and so missed this as I didn't check all the ones just matching "author". |
rsanchez87
added a commit
to fluendo/fluster
that referenced
this issue
Jan 15, 2025
…ne in PyPi web page (Open request here pypi/warehouse#12877)
Reopening because this is distinct from #9400 per #9400 (comment). |
rsanchez87
added a commit
to fluendo/fluster
that referenced
this issue
Jan 15, 2025
-Create pypi publishing CI workflow based on release tags -Remove poetry dependencies and some changes like the release version and python versions. -Add necessary dependency "setuptools-scm" to release.yml to include REPORT.md -Change version name to 0.2.0.0, read # TODO -Set absolute links for PyPI Website navigation after publishing a new release -Change order authors and maintainers to view only one in PyPi web page (Open request here pypi/warehouse#12877)
rsanchez87
added a commit
to fluendo/fluster
that referenced
this issue
Jan 15, 2025
-Create pypi publishing CI workflow based on release tags -Remove poetry dependencies and some changes like the release version and python versions. -Add necessary dependency "setuptools-scm" to release.yml to include REPORT.md -Change version name to 0.2.0.0, read # TODO -Set absolute links for PyPI Website navigation after publishing a new release -Change order authors and maintainers to view only one in PyPi web page (Open request here pypi/warehouse#12877)
rsanchez87
added a commit
to fluendo/fluster
that referenced
this issue
Jan 15, 2025
-Create pypi publishing CI workflow based on release tags -Remove poetry dependencies and some changes like the release version and python versions. -Add necessary dependency "setuptools-scm" to release.yml to include REPORT.md -Change version name to 0.2.0.0, read # TODO -Set absolute links for PyPI Website navigation after publishing a new release -Change order authors and maintainers to view only one in PyPi web page (Open request here pypi/warehouse#12877)
rsanchez87
added a commit
to fluendo/fluster
that referenced
this issue
Jan 16, 2025
- Change order authors and maintainers to view only one in PyPi web page (Open request here pypi/warehouse#12877) - add changelog: false to not update CHANGELOG.md in the CI process
rsanchez87
added a commit
to fluendo/fluster
that referenced
this issue
Jan 16, 2025
- Change order authors and maintainers to view only one in PyPi web page (Open request here pypi/warehouse#12877) - add changelog: false to not update CHANGELOG.md in the CI process
rsanchez87
added a commit
to fluendo/fluster
that referenced
this issue
Jan 16, 2025
-Automate release process completely taking advantage of semantic commits and already-created in GitHub actions - update version to publish - Change order authors and maintainers to view only one in PyPi web page (Open request here pypi/warehouse#12877) - add changelog: false to not update CHANGELOG.md in the CI process
rsanchez87
added a commit
to fluendo/fluster
that referenced
this issue
Jan 17, 2025
-Automate release process completely taking advantage of semantic commits and already-created in GitHub actions - update version to publish - Change order authors and maintainers to view only one in PyPi web page (Open request here pypi/warehouse#12877) - add changelog: false to not update CHANGELOG.md in the CI process
rsanchez87
added a commit
to fluendo/fluster
that referenced
this issue
Jan 20, 2025
-Automate release process completely taking advantage of semantic commits and already-created in GitHub actions - update version to publish - Change order authors and maintainers to view only one in PyPi web page (Open request here pypi/warehouse#12877) - add changelog: false to not update CHANGELOG.md in the CI process
rsanchez87
added a commit
to fluendo/fluster
that referenced
this issue
Jan 20, 2025
-Automate release process completely taking advantage of semantic commits and already-created in GitHub actions - update version to publish - Change order authors and maintainers to view only one in PyPi web page (Open request here pypi/warehouse#12877) - add changelog: false to not update CHANGELOG.md in the CI process
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
What's the problem this feature will solve?
👋 Hi. Our project
pyhf
just switched (c.f. scikit-hep/pyhf#2095) from having our PyPI metadata insetup.cfg
topyproject.toml
. In doing so, we also changed from having our author metadata for the 3 authors be acrossauthor
andauthor_email
to having it be contained inauthors
following PEP 621's requirements ofpip
is recognizing all the metadata as we would expectHowever, when we published this to TestPyPI to check how things looked after switching over we noticed that TestPyPI is displaying only the first author and linking their email
Previously when we shoved all our names and emails into
author
andauthor_email
we could at least have all our names be displayed (no surprise there as we were abusing the field)I assume that this behavior with
authors
is becausewarehouse
uses only the core metadata here (?) following PEP 621's instructions of:Would it be possible for
warehouse
to display all authors information if it exists? Or is that something that is outside the scope of howwarehouse
interacts with metadata?Describe the solution you'd like
Have
warehouse
be able to parse the existence of PEP 621authors
and display all names and associated emails ofauthors
on the package webpage.Additional context
The text was updated successfully, but these errors were encountered: