#15315 `poetry<=1.2.0b1` does not distinguish between `alpha` and `dev` releases Issue created by stuhood Attempting to consume

2.12.0a0

using

pants_requirements

in a repository using

[python].lockfile_generator=poetry

will hit python-poetry/poetry#4653, which causes

poetry

to create a lockfile containing

2.12.0.dev3

, which then cannot actually be consumed. • Temporarily switching to PEX for lockfile generation 1) only for the relevant resolve and 2) only in this release... seems to work: i.e.:

./pants --python-lockfile-generator=pex generate-lockfiles --resolve=pants-plugin

. • Using an explicit

python_requirement

target rather than

pants_requirements

does not work:

poetry

converts the

pantsbuild.pants==2.12.0a0

requirement into

2.12.0dev0

(whee). • Upgrading

poetry

to

1.2.0*

would probably fix this... although an end user is not able to do this, because they'll encounter an incompatibility in our shim. pantsbuild/pants