Ignas Anikevicius

Not sure what to do with the failing Windows tests. Any ideas?

Some thoughts about a better solution here: https://github.com/bazelbuild/rules_python/pull/1728#discussion_r1660617136 Not sure yet how to integrate the current `experimental_index_url` with the code snippet in there, but it would be an alternative that...

FYI, some PyPI packages have `musl` wheels being distributed next to the `manylinux` wheels which are `glibc`. Example: https://pypi.org/project/coverage/#files We should probably add a `libc` constraint somewhere to make sure...

With #1837 I have added `py_linux_libc` flag which I needed to handle `musllinux` wheels in select statements and this lead me to add `flag_values` to our toolchain platform definitions. With...

OK, since #1837 has landed and the bugs with toolchain selection got squashed, adding extra `musl` changes should be now indeed very easy. I personally don't have time to do...

FYI, right now this usecase might be supported by having three files: ``` # requirements.in -r requirements_1.in -r requirements_2.in # requirements_1.in numpy == 1.20.0 # requirements_2.in boto3 ``` And then...

~I think these are just flakes, restarted the jobs.~ EDIT: I could be wrong here, as they failed twice. EDIT2: I've read the linked commit message and it is really...

> FYI: I've opened [pypa/distutils#278](https://github.com/pypa/distutils/pull/278). I figure it's best to handle this upstream of `rules_python` if possible. I don't think the workaround is too nasty to merge in the meantime,...

I think this is something that you may want only if the gazelle roots are using the same requirements files, so this ask is not necessarily something that is useful...

Continuing the discussion her. I think the best way would be to support the default visibility directive that gazelle has to support your usecase. Just to ensure that we are...