Dependencies won't install if description contains new lines

[sirex]

• I am on the latest Poetry version.
• I have searched the issues of this repo and believe that this is not a duplicate.
• If an exception occurs when executing a command, I executed it again in debug mode (-vvv option).

• OS version and name: Manjaro Linux 20.2.1
• Poetry version: 1.1.4

Issue

When I create pyproject.toml file, that looks like this:

[tool.poetry]
name = "poetry-bug-repro"
version = "0.1.0"
authors = ["Me <me@example.com>"]
description = """\
Poetry bug repro.
"""
[tool.poetry.dependencies]
python = "^3.9"
requests = "*"

(Note the new line in the description). Then, when I poetry build it, and try to install wheel package, it won't install any dependencies, in this case it won't install requests.

But if I replace description to:

description = "Poetry bug repro."

Then dependencies are installed as expected.

I think, the issue is that when .dist-info/METADATA file is generated, it creates an empty line like this:

Metadata-Version: 2.1
Name: poetry-bug-repro
Version: 0.1.0
Summary: Poetry bug repro.

Author: Me
Author-email: me@example.com
Requires-Python: >=3.9,<4.0
Requires-Dist: requests

After this new line, after Summary, everything else is treated as package description, I guess.

[sinoroc]

This should be only one line:

• https://packaging.python.org/specifications/core-metadata/#summary

[sirex]

That is fine, if it should be only one line. But Poetry should refuse to build a corrupted package if given summary is not one line. At least, it should strip summary new line is only at the end of string.

[sinoroc]

agreed

[ekralc]

This has been addressed before in #1372

It seems that this is an edge case where 'multiline' strings that are actually a single line aren't caught.

For example, this fails as expected with a validation error:

description = """\
Multiple
line
description
"""

But any string with a single trailing newline is still allowed, resulting in an invalid MANIFEST.

[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.