hundreds-father-404
08/22/2022, 11:35 PM[python].resolve_all_constraints
until Pants 3.0 (but deprecated)? Originally, the plan was to remove it.pex_from_targets.py
is actually pretty minimal now. Note that we will always need to keep around a lot of the relevant code with how to subset via --repository-pex
because we decided to support manually managed requirements.txt-style locksenough-analyst-54434
08/22/2022, 11:39 PMwitty-crayon-22786
08/22/2022, 11:40 PM2.N+1
vs 3
is unclear, but is something that i think @flat-zoo-31952 was going to be looking into based on the audiencehundreds-father-404
08/22/2022, 11:42 PMwitty-crayon-22786
08/22/2022, 11:42 PMpex_from_targets
, i wouldn’t be hunting for things to deprecate anyway.enough-analyst-54434
08/22/2022, 11:43 PMhundreds-father-404
08/22/2022, 11:43 PMthis is not an end-user facing feature: rather, an admin. maybe that influences this.I think the most important thing here is that 3rd party requirements are complex and frustrating to deal with. We shouldn't force you to migrate, but we should encourage you to use the newer and safer thing
witty-crayon-22786
08/22/2022, 11:44 PMI personally consider them the same. Only big orgs have the differentiation.i don’t think that that is true. if a team of folks work in a monorepo, only one of them is going to land the upgrade PR.
enough-analyst-54434
08/22/2022, 11:44 PMwitty-crayon-22786
08/22/2022, 11:48 PMflat-zoo-31952
08/22/2022, 11:49 PMwitty-crayon-22786
08/22/2022, 11:50 PMeither data showing the item is legitimately a misfeature, or if it directly conflicts with progressyea.
flat-zoo-31952
08/22/2022, 11:51 PMhundreds-father-404
08/22/2022, 11:53 PMeither data showing the item is legitimately a misfeature, or if it directly conflicts with progress• misfeature: no, it's valid. only much worse than
[python].enable_resolves
• progress: not really, only makes our code harder to deal with. but it's factored well now