install.python-poetry.org with constraints.txt

[jackhamburger]

• [x] I have searched the issues of this repo and believe that this is not a duplicate.
• [x] I have searched the documentation and believe that my question is not covered.

Feature Request

Currently when running poetry-install.py for a specific version the dependencies of that specific poetry version are resolved at install time and may include recently published versions.

For example, poetry==1.1.11 required cryptography>=2.0 This has been incrementing to pull a newer and newer version of cryptography which ultimately broke a CI docker build I run when the newest version started requiring a rust compiler.

It would be great if we could deterministically install poetry - even if that required the 1-time generation of a poetry-install lock file.

[jackhamburger]

Actually a solution to my problem at hand was to prevent the install from trying to build the cryptography package wheel by adding "--prefer-binary" arg to the install command.

Potentially we could expose that as an option

[white-gecko]

Where do you add the --prefer-binary option? When I do curl -sSL https://install.python-poetry.org | python - --version "1.1.12" --prefer-binary I get an error error: unrecognized arguments: --prefer-binary.

RUN curl -sSL https://install.python-poetry.org | python - --version "1.1.12" --prefer-binary                                                                                                 1.3s
------
 > [3/3] RUN curl -sSL https://install.python-poetry.org | python - --version "1.1.12" --prefer-binary:
python-poetry/poetry#6 1.260 usage: - [-h] [-p] [--version VERSION] [-f] [-y] [--uninstall] [--path PATH]
python-poetry/poetry#6 1.260          [--git GIT]
python-poetry/poetry#6 1.260 -: error: unrecognized arguments: --prefer-binary

[Secrus]

What do you mean by poetry-install.py? We don't provide that script. Could you elaborate?

[neersighted]

I do believe this user is referring to install.python-poetry.org. Generating a requirements.txt or constraints.txt optionally as part of releases could be nice and is essentially what is being asked for here.

[vfazio]

Another vote for this feature. This becomes problematic for installs that need to compile dependencies, like cryptography, for environments that may not have a rust compiler (or do, but it's not up to date enough https://cryptography.io/en/latest/installation/#rust).

Installing poetry in an armhf environment (like rpi) with a piwheels source isn't enough because only some of the wheels are built (https://piwheels.org/project/cryptography/) and the ones that do have wheels cannot be pinned