Greg Roodt

Great! Yes, if that works for you, we may just consider that the recommended workaround and eventually close this issue.

> Maybe rename pip_parse to something else. Yes please. My favorite candidate is `pypi_install` > We should have a category of public but unstable API. Certain things should be called...

Does this post resonate with you @novas0x2a https://github.com/bazelbuild/bazel/issues/19645

> 1. Is there a better way of managing the installation of packages that must be built using source packages? You can consider pre-building wheels for your target platform(s) and...

I think in these scenarios, the best option is generally to work with and support the upstream package (eg pcslite) to fix packaging errors or make their packages easier to...

The comment from https://github.com/bazelbuild/rules_python/issues/1679#issuecomment-2243450876 is related, but also adjacent to the original issue. The original issue relates to the "runfiles" library specifically. This is a very narrow and special library...

It's probably a documentation issue, that wouldn't surprise me. Our examples are not great, but they do demonstrate the intended usage (and always have, while they've existed): e.g. https://github.com/bazelbuild/rules_python/blob/59bb4a88783cca738394cb3cb91bc8243df5e18d/examples/multi_python_versions/tests/my_lib_test.py#L18

Got it. If you can please raise a different issue for that? This specific issue is about the `runfiles` library that previously was encouraged to be used from inside rules_python....

> I'll go ahead and do that, but FWIW, I think that workspace name as prefixes is the correct way to go, and that if we fix that, we get...

The will be huge! Can’t wait. So many things can be improved if the rules can manage the bootstrap.