refined-dusk-58376
11/25/2020, 9:38 PMhundreds-father-404
11/25/2020, 9:42 PMblack
or pytest
What type of functionality are you hoping to add?refined-dusk-58376
11/25/2020, 10:12 PMpyproject.toml
) then install a dev version of the sub libraries on the root libraryhundreds-father-404
11/25/2020, 10:15 PMWhat I’m having problems with is just getting the bash plugin to work in my project.Hm, what types of problems? Happy to help with that
refined-dusk-58376
11/25/2020, 10:16 PMhundreds-father-404
11/25/2020, 10:18 PMpoetry export
to convert into requirements.txt files understood by Pants?refined-dusk-58376
11/25/2020, 10:19 PMrequirements.txt
files to help code move into production.hundreds-father-404
11/25/2020, 10:20 PMrefined-dusk-58376
11/25/2020, 10:20 PMhundreds-father-404
11/25/2020, 10:22 PMIt might be a possibility to create a bunch of small requirements.txt files to help code move into production.Yeah, Pants supports multiple requirements.txt. For each requirement.txt, you would have a BUILD file in the same directory with the macro
python_requirements()
, which converts each into a python_requirement_library
target
However, Pants currently only supports a single constraints file. A big feature request for Q4 is to support multiplerefined-dusk-58376
11/25/2020, 10:22 PMhundreds-father-404
11/25/2020, 10:23 PM./pants export
or ./pants vscode
periodically, and it will run all these steps? Note that this would be manual stillI’m mostly struggling with getting plugged in tasks working.What’s going on with the bash plugin not working?
refined-dusk-58376
11/25/2020, 10:26 PMhundreds-father-404
11/25/2020, 10:26 PM./pants help targets
will show if the target types are showing up./pants help subsystems
should show some new subsystems like shfmt
and shellcheck
refined-dusk-58376
11/25/2020, 10:31 PMhundreds-father-404
11/25/2020, 10:35 PMpythonpath
to the “source root”, e.g. if you have pants-plugins/bash/register.py
, and in your code you use import bash.register
, then set pythonpath
to pants-plugins
- you’ve activated all the backends in backend_packages
. In the above example, you would activate bash
refined-dusk-58376
11/25/2020, 10:44 PMhundreds-father-404
11/25/2020, 10:46 PMrefined-dusk-58376
11/25/2020, 10:50 PMbackend_packages
hundreds-father-404
11/25/2020, 10:51 PMrefined-dusk-58376
11/25/2020, 10:52 PMhundreds-father-404
11/25/2020, 10:56 PMAutomatically adding these things so I don’t have to think about it.Pants v1 was closer to this type of automatic registration. We registered all the builtin backends by default. But we found it was a really bad UX, as people wouldn’t know to opt-out so they would have irrelevant things like JVM support activated even if they never used it. As a design choice, backends are always opt-in in v2
refined-dusk-58376
11/25/2020, 10:58 PMhundreds-father-404
11/25/2020, 10:59 PMrefined-dusk-58376
11/26/2020, 2:23 AMhundreds-father-404
11/26/2020, 3:02 AMrefined-dusk-58376
11/26/2020, 3:59 AMhundreds-father-404
11/26/2020, 4:04 AMrefined-dusk-58376
11/26/2020, 4:05 AMhundreds-father-404
11/26/2020, 4:06 AMrefined-dusk-58376
11/26/2020, 4:13 AM