Ignas Anikevicius
Ignas Anikevicius
Please provide logs and a small reproduction example. The fact that our CI works on Windows seems like something is different in your environment.
when using bzlmod, py_library always uses the default python toolchain for figuring out dependencies
See the multi-version example to force a particular Python version. In `bzlmod` the version-aware toolchain is used by default specifically for this usecase. Let me know if that works for...
when using bzlmod, py_library always uses the default python toolchain for figuring out dependencies
Cleaning up old issues.
Could you please post a minimal reproduction for us to better understand why you need to add the `gazelle` directives? That is usually not needed.
This patching should be done in the invocations to the `http_archive` in `python/pip_install/repositories.bzl` in order work properly. We are not downloading the `installer` via the `pip` extension because the extension...
I would be still interested in getting to the root cause of this. I thought that whenever we setup a new package, we are doing this in a clean directory...
Thanks for digging this a little more. I'll close this as it is an upstream issue. If othecs feel strongly about including the patch in rules_python, let me know.
> This sounds like an issue that was introduced in [v4.3.0](https://github.com/golang-migrate/migrate/releases/tag/v4.3.0). > Namely, after `Migrate.Drop()` is called, the schema version table is no longer recreated. > > Maybe we should...
Right now it only needs the second entry, but we can handle a requirements file with both entries. To be concrete, `rules_python` is parsing each entry in the `requirements.txt` and...
`rules_python` cannot read dependencies from `pyproject.toml` yet and we depend on all of the transitive dependencies being in the `requirements.txt` file with their hashes. Something similar to [this](https://github.com/bazelbuild/rules_python/blob/main/examples/bzlmod/tests/dupe_requirements/requirements.txt). Ideal file...