Ignas Anikevicius
Ignas Anikevicius
FYI, the last time I did this we got a few regressions for pip compile. I'll dig for issues later.
FYI, the previous bump got reverted here: https://github.com/bazel-contrib/rules_python/pull/2584 It has the links to the issues that we encountered. See the comment: https://github.com/bazel-contrib/rules_python/issues/908#issuecomment-2612799169
In order to be comfortable to merge this I would like to have a regression test for the #908 issue. And the CI ideally should not be failing due to...
It seems that latest pip is incompatible with `pip-tools`: https://github.com/jazzband/pip-tools/issues/2252
A workaround is to use the Label `@pip_torch//:my_added_target`.
I meant that this is a way to get it working. Another option would be to use whl_filegroup rule to extract the libs from the whl target and then create...
I had some code laying around with using the uv binaries directly, so I took the liberty to push that here.
FYI, @groodt, I have created #2006 to move the remaining of the PyPI related code to `python/pypi` where we are re-exporting the publicly consumable symbols. I think we should clean...
My vote would be to keep everything in this PR under python/private, so that we have time (a few more PRs) to iron out the interfaces and docs. I would...
Your plans sounds good. :) thanks for working on this! On 28 June 2024 21:35:37 GMT+09:00, Greg Roodt ***@***.***> wrote: >> My vote would be to keep everything in this...