quiet-army-59227
06/20/2024, 7:37 PM.json
file into my pants.toml
file but it doesn't seem to be working. For example:
# pants.toml
[python.resolves]
pants-plugins = "@?pantsbuild/pants-plugins-config.json"
[python.resolves_to_interpreter_constraints]
pants-plugins = "@?pantsbuild/pants-plugins-config.json"
# pants-plugins-config.json
{
"resolves.pants-plugins": "SOME_PATH/pants-plugins.lock",
"resolves_to_interpreter_constraints.pants-plugins": ["==3.9.*"]
}
This creates the pants-plugins
resolve in @?pantsbuild/...
meaning is it not parsing the file and it is just taking the string literally. Same issue with resolves_to_interpreter_constraints.pants-plugins
Reference: https://www.pantsbuild.org/2.21/docs/using-pants/key-concepts/options#reading-individual-option-values-from-filesbroad-processor-92400
06/21/2024, 7:06 AMpants.toml
option structure.
I think this means it would need to be something like:
`pants.toml`:
# pants.toml
[python.resolves]
pants-plugins = "@?pantsbuild/pants-plugins-resolves.txt"
[python.resolves_to_interpreter_constraints]
pants-plugins = "@?pantsbuild/pants-plugins-interpreter-constraints.json"
`pantsbuild/pants-plugins-resolves.txt`:
SOME_PATH/pants-plugins.lock
pantsbuild/pants-plugins-interpreter-constraints.json
["==3.9.*"]
However, it seems a bit strange to use files for such small options, instead of just putting them in pants.toml
directly.
Can you give more background on what you're trying to achieve?quiet-army-59227
06/24/2024, 10:03 PMbroad-processor-92400
06/24/2024, 11:48 PM