Does anyone have any idea how I can test a change to migrate-call-by-name without needing to do a release?

oss/pants-migrate-script % pants migrate-call-by-name --json ../pants-plugins/pants-plugins/experimental/scie::
gives
pants.base.specs_parser.SpecsParser.BadSpecError: Relative spec path oss/pants-migrate-script/./../pants-plugins/pants-plugins/experimental/scie escapes build root oss/pants-migrate-script

BUT, on the flipside, going into

pants-plugins

and using

PANTS_SOURCE=../pants-migrate-script

works fine. However, in pants-plugins using the latest release, calling

pants migrate-call-by-name

gives me the same spec error... So, not really sure how to test this

oss/pants-plugins % pants migrate-call-by-name pants-plugins/experimental/scie:: 

ValueError: 'Caches/nce/8fb836cadd1e1f50180fea66b6acab1f23108e9a74f158744e706c6da41a534b/bindings/venvs/2.29.0rc0/lib/python3.11/site-packages/pants/core/util_rules/system_binaries.py' is not in the subpath of '/Users/sj/Developer/scratch/oss/pants-plugins' OR one path is relative and the other is absolute.

Ditto if I use absolute paths - I'm currently operating on editing the cached source or something silly

A thought: You could build a Pants PEX locally and then point the

pants

launcher at it with a

file://

URL?

I thought about it - but the time taken to fix it in my cached env was just so much faster 😆