tree e87a7efa4e8f5f5a7594bfb9966d306423e68bd7
parent 847c03f6e830a792a2b9d97e10928268962a7fcb
author Richard Levasseur <rlevasseur@google.com> 1702687162 -0800
committer GitHub <noreply@github.com> 1702687162 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlfPHKCRBK7hj4Ov3rIwAA4UQIAKc7j66W9bKZcTy3bw+fVEqE
 roxyZOeFHRlGFgnpjJKYwDnmQZf102sedgoSAZ1Ahuv+hT1buiBEfS75bi8Ia5Bv
 kM4yzKIHNXxsinslNxG6kiLHDii3bTciFfbLUrRTC2N2ZsZofQR3BVOogHp97ULI
 6jfnRJloDz1OqBKlt8gnMnsF3L5OevnIxtBHlrOOL4FtFSx4UDliSY/Z1E9Sjbh7
 +kLD0vKTnNz7BcwS7PfnJwivGSHp4bjjb2VAWug53XJxwUusMU0vdC0NhI1HHlIV
 9o6ULs5zaqRdlWG7amjwNpaPdhUx3gOLIoxUumElmNm4DVLY13JrcGzJEHTiQcA=
 =dtu6
 -----END PGP SIGNATURE-----
 

fix(pip.parse): allow absolute path for python_interpreter; skip hermetic toolchain lookup when used (#1619)

The `python_interpreter` arg wasn't being properly handled in the bzlmod
code in two ways.

1. Lookup of a hermetic runtime wasn't being skipped when it was set.
The net effect was it
ignored the specified interpreter and would try to lookup a hermetic
interpreter using
the python version. To fix, add a check for python_interpreter to the
guard of the lookup.

2. Specifying an absolute path for the value wasn't being converted to a
`path` object,
which meant a plain string eventually made its way to some code
expecting a `path`
object. To fix, call `repository_ctx.path()` on the path to convert it
to a path object.

Fixes https://github.com/bazelbuild/rules_python/issues/1618