high-yak-85899
08/30/2023, 6:59 PM[WARN] DEPRECATED: indirectly referring to a target by using a corresponding file argument, when the target owning the file isn't applicable is scheduled to be removed in version 2.18.0.dev1What's the background on this one? I find it incredibly convenient to not have to remember what the target address is in the build file.
bitter-ability-32190
08/30/2023, 7:00 PMpackage path/to/file.pybitter-ability-32190
08/30/2023, 7:00 PMhigh-yak-85899
08/30/2023, 7:01 PMpants run path/to/file.pyhigh-yak-85899
08/30/2023, 7:01 PMpython_sources (obvi) and a pex_binaryhigh-yak-85899
08/30/2023, 7:01 PMhigh-yak-85899
08/30/2023, 7:01 PMpex_binary since it wasn't needed, though.bitter-ability-32190
08/30/2023, 7:01 PMhigh-yak-85899
08/30/2023, 7:03 PMbitter-ability-32190
08/30/2023, 7:03 PMbitter-ability-32190
08/30/2023, 7:06 PMbitter-ability-32190
08/30/2023, 7:08 PMbitter-ability-32190
08/30/2023, 7:09 PMhigh-yak-85899
08/30/2023, 7:10 PMbitter-ability-32190
08/30/2023, 7:40 PMrun is special in that it only ever expects to match one target. The core code this warning gets raised from doesn't know what context it's being called from thoughbitter-ability-32190
08/30/2023, 7:42 PMTargetRootsToFieldSetsRequestbitter-ability-32190
08/30/2023, 7:42 PMwitty-crayon-22786
08/30/2023, 7:45 PMbitter-ability-32190
08/30/2023, 7:51 PMbitter-ability-32190
08/30/2023, 8:23 PM