#general
Title
b
big-fall-51153
05/28/2021, 3:16 PMAm I correct in understanding/thinking that I can't generate `setup_py`'s
namesetup_pyPythonArtifact.__init__My use case is I'd like to be able to read in that value from a file so I can DRY up project configuration. I need to be able to separately read in that value from another script, hence the separate file
e
enough-analyst-54434
05/28/2021, 3:55 PMSo, you're treading into an interesting and dangerous area that is not (well?) supported yet. The fundamental gotcha to contend with is Pants must be aware of the file the name comes from so it can change-track that file to know when it needs to re-run rules that consume the name value. In spirit you need a rule that generates a python_distribution target - or some of its fields. In practice, we have no such 1st class facility for generating target metadata from (non-BUILD) files and we use a hack via macros (https://www.pantsbuild.org/docs/macros). An example of the hack can be read here:
1. Hack target to own file name will be read from: https://github.com/pantsbuild/pants/blob/a2e7ecf55f78d0611ff43c7db8d6a43cb570c86b/src/python/pants/backend/python/target_types.py#L650-L653
2. Hack dependency wiring / target generation in a macro: https://github.com/pantsbuild/pants/blob/dee363930f4d4f37438695128e082a1266253d26/src/python/pants/backend/python/macros/python_requirements.py#[…]4
3. Registering the Hack target and Hack macro:
a. https://github.com/pantsbuild/pants/blob/311419b50a36743c284e27af20053fb7ae9e0925/src/python/pants/backend/python/register.py#L44-L52
b. https://github.com/pantsbuild/pants/blob/311419b50a36743c284e27af20053fb7ae9e0925/src/python/pants/backend/python/register.py#L76-L82
There is alot to digest in the hack, so fire away if you have questions after absorbing all that.
b
big-fall-51153
05/28/2021, 4:17 PMSeems to be a pattern in the things I'm trying to do 😂
Thanks, I'll see if that works out
e
enough-analyst-54434
05/28/2021, 4:23 PMIf your usage pattern involves tools outside Pants control interacting with / working along side Pants then it will continue to be a theme I think. We have assumed we're in control for the most part. It's good to have use cases like yours push on these assumptions.
b
big-fall-51153
05/28/2021, 4:47 PMThis is a script local to the repo, so it could be pulled into a pants goal - the purpose of the script is to generate a new version, version the changelog, and then git-tag. It could easily be a "codegen" plugin
e
enough-analyst-54434
05/28/2021, 5:12 PMAh, yeah - this is a common need. We have not tried to wade in here yet since folks have a fair bit of variation in how they handle publishing. In Pants v1 we did weigh in for the jvm. That supported:
1. Auto-publish: i.e.: run
./pants publish ::