Only the first author and maintainer are included in metadata of packages built with poetry when multiple are listed

[mhamiltonj]

• Poetry version: 1.3.1
• Python version: poetry: 3.10.6; venv: 3.8.3
• OS version and name: Windows 10 build 19044
• pyproject.toml: https://gist.github.com/mhamiltonj/b69bce33995561bb71cefc477f06659b

• I am on the latest stable Poetry version, installed using a recommended method.
• I have searched the issues of this repo and believe that this is not a duplicate.
• I have consulted the FAQ and blog for any relevant entries or release notes.
• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option) and have included the output below. - No exception raised

Issue

I have defined multiple authors and maintainers under [tool.poetry], (see below) but after building with poetry build, only the first of each is listed in METADATA in the wheel, and in PKG-DATA in the sdist. I can find only one other reference to this problem, in this stack overflow question with no resolution: https://stackoverflow.com/questions/72003628/why-cant-i-have-multiple-authors-after-build-with-poetry-in-pkg-info

[tool.poetry]
    name="our-project"
    readme = "README.md"
    license = "LGPL-3.0-only"
    version = "0.1.0.post3"
    authors = [
        "Author 1 <[email protected]>",
        "Author 2 <[email protected]>",
        "Author 3 <[email protected]>"
    ]

    maintainers = [
        "Maintainer 1 <[email protected]>",
        "Author 3 <[email protected]>"
    ]

Reults in this METADATA

Metadata-Version: 2.1
Name: our-project
Version: 0.1.0.post3
Summary: ...
License: LGPL-3.0-only
Author: Author 1
Author-email: [email protected]
Maintainer: Maintainer 1
Maintainer-email: [email protected]
Requires-Python: >=3.8,<3.9
Classifier: License :: OSI Approved :: GNU Lesser General Public License v3 (LGPLv3)
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.8
...

full (sanitised) pyproject.toml here: https://gist.github.com/mhamiltonj/b69bce33995561bb71cefc477f06659b

[dimbleby]

so far as I can see the metadata only allows a single author and maintainer - see https://packaging.python.org/en/latest/specifications/core-metadata/#author and https://packaging.python.org/en/latest/specifications/core-metadata/#maintainer

NB fields that are allowed to be repeated are annotated as "multiple use" in that document.

Can you spell out what you are expecting poetry to do?

[mhamiltonj]

so far as I can see the metadata only allows a single author and maintainer - see https://packaging.python.org/en/latest/specifications/core-metadata/#author and https://packaging.python.org/en/latest/specifications/core-metadata/#maintainer

NB fields that are allowed to be repeated are annotated as "multiple use" in that document.

Can you spell out what you are expecting poetry to do?

I will admit I hadn't checked the metadata specs. I assumed that since both poetry and PEP 621 allow multiple values for authors and maintainers in pyproject.toml, that obviously that would be reflected in the metadata of packages built based on pyproject.toml. Not a poetry issue, sorry for the noise

[sinoroc]

Related: https://discuss.python.org/t/pep-621-round-3/5472/87

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.