Jonathon Belotti

@hrfuller Yep this is totally expected with the python-build-standalone intepreter. > pip_install fails for only one requirement `tree-sitter` from `requirements.txt` It's failed to find a wheel for `tree-sitter` so fell...

> Seems like this will allow for using in-workspace py_runtime definitions as long as the interpreter is specified explicitly in the parfile() rule. If you have an in-workspace interpreter at...

Thanks for the issue report @blais, and sorry for the delayed response. This does look like something that should be more official. Links to the files mentioned: * **tensorflow/tensorflow** [`third_party/py/python_configure.bzl`](https://github.com/tensorflow/tensorflow/blob/9ca9a4f8e9b4d60408a092db4320805711367042/third_party/py/python_configure.bzl)...

@hrfuller is this related to something you experienced at Twitter? We use Tensorflow at my company but not TFX, and so wouldn't have seen this.

Don't close. This is still a problem when using the non-hermetic default Python toolchain. When toolchain support is better supported here was can document the problem with the default toolchain,...

`pipenv` actually vendored a bunch of the `pip-tools` code I think. So yeah it pre-dates. We used to use Pipenv with Bazel but abandoned it in favour of pip-tools because...

@juliexxia has the been any movement internally at Google on a transition to Starlark-based rules? This is an important change that can't really happen without a lot of coordination between...

@dayfine I think this is a good setup. I tried the same at work and ran well, but we strictly avoid pulling platform-dependent packages and `notebook` uses `appnope==0.1.0` which is...

We don't use relative imports anywhere in our Bazel workspace. They're not worth the trouble imo, and I wouldn't be surprised at all if implementation details in Python rules made...

@doubler We used to use that `imports` attr but I think it's a code-smell. For our use cases we've been able to move to absolute imports and remove all use...