#pip-tools

1 messages ยท Page 1 of 1 (latest)

strong falcon
#

๐ŸŽ‰

elfin glen
#

I suppose there are no known tricks beyond installing pip-tools into the project's virtualenv to convince it to consider a specific python version?

strong falcon
#

Yeah, It's general advice to have pip-tools installed in your venv. However, you can also use globally installed pip-tools (or installed via pipx) -- there should be no difference for pip-compile. Globally installed pip-sync would require --python-executable option to point a specific python interpreter.

#

to convince it to consider a specific python version

To use specific python version, yeah, pip-tools should be installed there so that pip-compile could resolve deps in this environment.

#

AFAIK there are no other options to convince pip-compile to use a particular Python version.

static plaza
clear salmon
elfin glen
#

@clear salmon i thought so, sadly not ๐Ÿ˜ฆ

strong falcon
#

@elfin glen could you check this PR https://github.com/jazzband/pip-tools/pull/1898 ?

$ echo click | pip-compile - -qo- --no-header --no-annotate
click==8.1.3

$ echo click | pip-compile - -qo- --no-header --no-annotate --pip-args='--python-version=3.0.0'
click==6.7
abstract stump
strong falcon
strong falcon
#

@abstract stump is everything allright? xD

abstract stump
#

i don't quite get the all extras logic in pip-compile. if there are multiple src_files, we don't collect extras from all of them, since we reassign extras. but the good news is that this will fail loudly if it's a real bug

strong falcon
strong falcon