poetry-core 1.3.2 not backwards compatible when using poetry build

• Poetry version: 1.2.0b1

• poetry-core version: 1.3.2

• Python version: 3.7.2

• OS version and name: macOS 10.15.7

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

Issue

With poetry-core version 1.3.2, when running poetry build on my project, the naming of the sdist zip file is all lower case. Eg. myPackage becomes mypackage-0.1.0.zip instead of myPackage-0.1.0.zip. This caused an issue in our pipeline due to the casing of the package name.

I understand that lower case is the PEP standard, but is it expected that the newest version of poetry-core is not backwards compatible? I had to revert to poetry-core 1.2.0 to fix this issue.

Thanks!

[neersighted]

The exact version numbers are a bit off, but yes, pinning to 1.2.1 will give you the previous sdist naming.

[blueraspberrypie]

I think we agree then. In general sdist names were underspecified and unstable; we’ve solved the issue of uploads by backporting the change to use the new canonical naming.

In any case, there’s nothing to be done here regarding the change in behavior in an old pre-release. There should be no unexpected changes when pinning to a regular release, but when you pin to a pre-release, unexpected breakage due to a core change may happen.

This makes sense to me 😃 If I pin to poetry 1.2.1 instead, it will only use poetry-core 1.2.0 and not upgrade to poetry-core 1.3.2, unless I upgrade to poetry 1.2.2, is this correct?