Ignas Anikevicius comments

Results 504 comments of


                                            Ignas Anikevicius

_test.py files being included in py_library rather than py_test

If #999 is not sufficient, please reopen this ticket.

Allow pip_repository (and pip_parse) to "select" requirements based on both OS and architecture

FYI: #1593 added `whl_library` ability to point to dependencies that are platform specific, now we need installing of dependencies based on the target platform, that is further away. I had...

Allow pip_repository (and pip_parse) to "select" requirements based on both OS and architecture

@thomasegriffith, thanks for the comment. What is your usecase for having different requirements files? I'd like to know a little bit more about how people use this feature. I would...

"Cross compilation" of py_binary/py_image/py_library targets

I am looking to fix this for `bzlmod` in #1643 at least for the `whl` downloading part, I'll leave this ticket to track the `sdist` cross-compilation.

Support coverage for `py_test`

I think we can safely close it now as we have docs and there are quite a few versions supporting toolchain with coverage.py enabled.

Support coverage for `py_test`

See https://rules-python.readthedocs.io/en/latest/coverage.html

patch a `pip_install`

Support of wheel patching should work on `bzlmod` now with `0.27.0`: https://github.com/bazelbuild/bazel-central-registry/pull/1138

patch a `pip_install`

FYI, for legacy WORKSPACE users it is technically possible to pass whl_patches argument to install_deps() call in your WORKSPACE. The API is not something we want to make a promise...

Python code formatting rule

I would be interested in this functionality as well.

We have our internal rule as well, but looking at the `rustfmt` [source](https://github.com/bazelbuild/rules_rust/blob/main/rust/private/rustfmt.bzl) I see that it is much more solid. Our current approach is a custom `_test` rule for...