hundreds-father-40408/22/2022, 11:35 PM
until Pants 3.0 (but deprecated)? Originally, the plan was to remove it.
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
because we decided to support manually managed requirements.txt-style locks
enough-analyst-5443408/22/2022, 11:39 PM
witty-crayon-2278608/22/2022, 11:40 PM
is unclear, but is something that i think @flat-zoo-31952 was going to be looking into based on the audience
hundreds-father-40408/22/2022, 11:42 PM
witty-crayon-2278608/22/2022, 11:42 PM
, i wouldn’t be hunting for things to deprecate anyway.
enough-analyst-5443408/22/2022, 11:43 PM
hundreds-father-40408/22/2022, 11:43 PM
this 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-2278608/22/2022, 11:44 PM
I 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-5443408/22/2022, 11:44 PM
witty-crayon-2278608/22/2022, 11:48 PM
flat-zoo-3195208/22/2022, 11:49 PM
witty-crayon-2278608/22/2022, 11:50 PM
either data showing the item is legitimately a misfeature, or if it directly conflicts with progressyea.
flat-zoo-3195208/22/2022, 11:51 PM
hundreds-father-40408/22/2022, 11:53 PM
either data showing the item is legitimately a misfeature, or if it directly conflicts with progress• misfeature: no, it's valid. only much worse than
• progress: not really, only makes our code harder to deal with. but it's factored well now