Keith Smiley
Keith Smiley
maybe a cool way to make this work could be to use something like `--run_under=@rules_python//some:label` which acted as an abstraction for setting whatever internal env vars or something necessary to...
I'm thinking maybe the label we set would just be a shell / py script that did an `export` and exec'd the args
should we merge?
related to https://github.com/aspect-build/rules_py/commit/f2240acff1976373b6da86be2e9d962f926bade9#diff-6878df526d6e39f46c6e953f0cfcc2e5b7938d5c4d2cbec0657e78c99b931239R2
I can't tell if this is something rules_pycross already supports with poetry or not, I might try that to see if it's similar
looks like poetry actually fails in that case since it uses the version info for this instead, and that is expected to be a type that it is not
an alternative solution for this would be for me to somehow inject the label for the dep, that might be a transitive of other deps, so that I could handle...
I think it's an entirely separate concept borrowing the same terminology. I think the goal of it is just to allow you to install different versions of things based on...
this requires a toolchain change in order to add a test, I can do that if folks are happy with this direction
see the alternative here https://github.com/bazelbuild/bazel/pull/25751