SyntheticTarget addresses are determined before BU...
# development
p
SyntheticTarget addresses are determined before BUILD files get parsed, right? So, I can't reference anything in a BUILD file when creating a SyntheticTarget? Context: I'm looking into creating SyntheticTargets in the same directory where
python_distribution
targets are defined. But it looks like the SyntheticAddressMaps processing happens before BUILD files get processed.
1
c
yea.. sort of. If you "know" an address will exist, then you can reference it, but you can't look it up, as you say, the synthetic targets are created in tandem with parsing BUILD files.
p
That's what I thought / was afraid of.
Thanks for confirming.
👍 1
c
I'll throw in a few brain cycles on your entry points question.. see if anything jumps out 🙂
(feels kind of invasive to turn the python_distribution target into a generator for the purpose.. but idk of anything better to do, so..)
p
yeah... My experiments with wiring that up have run into a lot of roadblocks. I've posted my latest thoughts here: https://github.com/pantsbuild/pants/issues/15481
👌 1
c
I like the annotated dependencies approach.. would be nice if we could generalize it for any dependency in some way, that would be immensely useful 🙂
p
Yeah. I've beat my head on annotated dependencies several times as well. I'm just not sure what the interface for that might look like. Plus, annotating dependencies has been discussed as a tangent on other topics, so that discussion is spread out so I lose track of where I read what.
💯 1
To be clear: I really like the idea of annotating the dependencies.
👍 1
c
yea, it's more work, for sure. so I guess it comes down to how "urgent" this entry points fix is..