Python 3rd party deps page rewritten to talk about Poetry vs Pex lockfiles, along w/

parametrize

in the context of multiple resolves. Feedback/questions welcomed! https://www.pantsbuild.org/docs/python-third-party-dependencies#lockfiles

Yeah, not the blog. This may be a question that has a more natural answer from the docs overhaul. e.g. a dedicated Tutorials section or something. Gordon's Django tutorial and SJ's plugins tutorial likewise would make sense there.

Pants docs are tricky because often you don't need much information, but when you do, you do. I suspect efficient use of links will be helpful For example, I've been thinking about what an on boarding guide will look like. Often you don't even really have to worry about source routes if you use the default. But when you need it, you need it. So I think the tutorial will make liberal use of linking to more detailed pages when you need it

looks great! my largest bits of feedback are: 1. maybe move the whole Multiple Lockfiles section down to Advanced Usage? 2. rather than updating all of the thirdparty targets you want in the resolve first, you’d probably: a. start by updating whichever requirement(s) you know need to be different in the new resolve b. then update the firstparty targets that you know need the different requirements. c. then, iterate on getting the firstparty targets building… which will involve adding both firstparty and thirdparty targets to the resolve ---- other minor feedback:

If you want a different location, change [python].resolves like this:

would use the TOML table syntax here the same way you do in the “multiple resolves” section.

If you use Pex-generated lockfiles

at this point on the page, there hasn’t been an explanation of what a PEX lockfile is: should link to the setting probably.

While it’s often desirable to have a single lockfile for the whole project

would differentiate between a project and a repository: a monorepo usually has multiple projects/binaries/apps in one repository.