hundreds-father-40403/09/2022, 4:44 PM
to always generate using Pex JSON. But do we think it's valuable to indefinitely let users keep manually generating their requirements.txt style lockfiles, e.g. via pip-compile or poetry export?
bitter-ability-3219003/09/2022, 4:55 PM
hundreds-father-40403/09/2022, 4:57 PM
bitter-ability-3219003/09/2022, 5:01 PM
hundreds-father-40403/09/2022, 5:03 PM
bitter-ability-3219003/09/2022, 5:14 PM
hundreds-father-40403/09/2022, 5:16 PM
, but not regenerate what you already have. Pants needs to support that imo.
bitter-ability-3219003/09/2022, 5:37 PM
hundreds-father-40403/09/2022, 5:40 PM
bitter-ability-3219003/09/2022, 9:24 PM
into PEX json and keep the same versions (
) I'm much tolerable to sunsetting all support of pip-style txt file, assuming users are made aware of the migration mechanism and it works as expected.
pex3 lock create --requirements reqs.txt -o foo.lock
./pants generate-lockfiles --migrate
hundreds-father-40403/09/2022, 9:36 PM
have weird quirks like environment markers. I'm not very confident that we want people using that as the input to regen lockfiles I think it's helpful to offer as an option, but an option that you might not need or want to use
bitter-ability-3219003/10/2022, 2:06 AM
before, so maybe a solution built into
doesn't make a whole lot of sense 😅