Fetching tool requirements from a requirements file

[AbdealiLoKo]

Can I generate [flake8].extra_requirements from a requirements.txt file ?
Instead of hardcoding it in the pants.toml ?

I just have a lot of requirements files I have right now (requirements-flake8.txt, requirements-pytest.txt, etc)
And was wondering if I can reuse them instead of rewriting them in a config file which is pants specific

[thejcannon]

So Pants uses pex to make lockfiles, so you should be able to lock like Pants does, and tell Pants to ignore the missing metadata.

• Tell Pants to ignore missing metadata (unfortunately global): Set [python].invalid_lockfile_behavior = "ignore"
• If you plan on just doing it yourself, you can install pex on your machine. Otherwise you'll need to sandbox pex in a pex_binary (which is a much longer explanation I plan on blogging about later). Note that Should we expose internal (python) tools as targets? #17336 would solve this in a very convenient way.
  • One caveat is to make sure you're using the version of pex equal or lower than Pants is, or else you might use newer metadata than Pants' PEX knows how to use. https://www.pantsbuild.org/docs/reference-pex-cli (for your version) has the version option and the default is what Pants is using. Alternatively you can bump that up because PEX is always backwards-compatible.
• Then run pex3 lock create -r <requirements.txt> -o <output.lock> with your input and output (output would be your setting of [<tool>].lockfile