rough-engineer-58925
11/14/2024, 10:55 PMrequirements.txt
that cover my codebase subset from step 2.
I found that I could use pex_binary
for step 2. It's suboptimal because I only care about the python files, and generated proto code but I can live with that.
I don't know how to do (1), (3), and (4).rough-engineer-58925
11/14/2024, 10:58 PMmy_config_rule(name=str, configs=dict[str, str])
The output of my_config_rule
should be a json file:
{
# Other omitted key values
# The other values come from a fixed template.
"configs": <configs from rule>
}
elegant-florist-94385
11/14/2024, 11:14 PMrough-engineer-58925
11/15/2024, 8:48 PMrough-engineer-58925
11/15/2024, 8:48 PMcareful-address-89803
12/05/2024, 2:18 AMGet(SourceFiles, ...)
. There's already machinery to get a list of Python requirements (I'd have to look up the specifics). And you can just make files whenever you want with CreateDigest
.
Without a plugin, I could imagine trying to use a script that chains pants dependencies --transitive
and pants peek
. But it would honestly be much easier with a plugin.careful-address-89803
12/05/2024, 2:21 AMrough-engineer-58925
12/06/2024, 11:19 AMflaky-artist-57016
01/20/2025, 6:51 PM