I have another related question. Suppose I have a python mono repo and I want to release a python library package. At the moment, I specify requirements in setup.cfg (or requirements.in) then use pip-compile to produce a requirements.txt which pants then consume to generate requirements target. For example, in requirements.in

boto3-stubs[ec2]

And in requirements.txt

boto3-stubs==1.28.85
botocore-stubs==1.31.85
mypy-boto3-ec2==1.28.85
types-awscrt==0.19.10
types-s3transfer==0.7.0
typing_extensions==4.8.0

Now if I have a python distribution that uses that library:

python_sources(name="src")

python_distribution(
    name = "dist",
    dependencies = [
        ":src"
    ],
    provides=python_artifact(
        name="my-package",
        version="0.0.1",
    ),
    repositories = [
        "@codeartifact"
    ],
)

The produced python package will have dependencies like the following:

mypy-boto3-ec2==1.28.85

Obviously my library don’t really need that specific pin. What is the recommended way to configure the pants setup so that 1. I have an easy way to define dependencies (e.g. just specifying deps without strict version bounds in requirements.in) 2. Configure that the produced package artifact doesn’t need to have the == bounds on the dependencies