Hi, I wonder whether

poetry_requirements

supports wildcard specification. In migrating a project using pants, I took the existing pyproject.toml as is, which contains, e.g.

pillow = "*"

in the declarations. After generating the user lockfile using

poetry export

and configuring the constraints file in the

pants.toml

, I received an error saying that

pillow==*

can't be satisfied while building. I've verified that poetry has correctly exported the resolved version for that package in constraints.txt. I hope I followed the right steps when using

poetry_requirements

in pants. It's not a blocker for me though as a wildcard can always be rewritten to

>=0.0.0

or some known version as the lower bound in pyproject.toml. But it would be nice if pants could have it supported.

Looks like we don't handle this, and treat

= "*"

as if

*

were a specific version.