poetry-core 2.0.1 installs fewer files

[0-wiz-0]

Description

After updating poetry-core to 2.0.0 (or 2.0.1, the updates were close together, I'm not quite sure) in pkgsrc, some packages using it installed fewer files than before.
Examples:
beets 2.2.0
construct-classes 0.1.2
fritz_exporter 2.3.1
sydent 2.6.1
test-textual-snapshot 1.0.0
pypika-tortoise 0.3.2

Is this change intended by poetry-core or a bug?

If intended, can you please advise how the projects should be fixed?

Thank you.

Workarounds

Install the files manually :-)

Poetry Installation Method

system package manager (eg: dnf, apt etc.)

Operating System

NetBSD

Poetry Version

2.0.1

Poetry Configuration

n/a

Python Sysconfig

See above.

Example pyproject.toml

See above.

Poetry Runtime Logs

Command is not failing.

[dimbleby]

Bug report unclear - I don't know what the connection between those logs and poetry is?

But yes there are breaking changes ar 2.0 re what files are included, please read the release announcement

[Secrus]

poetry-core had the includes system refactored with 2.0. Could you check your package includes, as that is the most likely cause of the breakage on your end?

Since this concerns a different kind of packaging/repackaging system, I am going to close this issue. If you find that there is still some issue about what files are not found in the build artifact, please create a reproduction.

[0-wiz-0]

We're using python -m build --wheel to build wheels and then install them with installer. This hasn't changed.
The linked files show which files are not installed any longer, you can ignore the rest.
I did read the CHANGELOG and the pinned issue #9136 but didn't find the relevant item. Can you be more explicit please?

[Secrus]

@0-wiz-0 unless you find some irrefutable proof that poetry-core is at fault, you should first check with the project you see changes in. The includes change I was referring to is this.

[Secrus]

1. include and packages are not the same things.
2. These files shouldn't be included in the wheels, since on installation they would be put in the site-packages directory, where they would clash with files from other packages. If you want the previous behavior, the easiest fix would be to pin your backend to <2 version. Otherwise, you have to add { path = "<file/dir path>", format = ["sdist", "wheel"] } for each of the include entries.

[0-wiz-0]

Thank you for the explanations.
I agree that this is a net positive change

For me it was hard to find out from the Changelog.
I suggest that in the future changes will not only be described on the source level but also on the result level.
If you don't know what includes are, changes to include handling will not let you guess that this means changes in the installed files by a binary wheel.

Thanks.

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