[feature]: Windows support

[peakschris]

What happened?

Using rules_py on Windows via MODULE.bazel fails with the following message:

I see this with all versions from 1.4.0 to 1.6.6. MODULE only. Bazel 8.4.1.

With py_venv in my BUILD.bazel:

>bazel test //...
INFO: Invocation ID: 8e301fb2-9e5e-40e3-9afb-deb9f757fc2f
ERROR: error loading package '@@aspect_rules_py+//py/tools/venv_bin': at D:/udu/b/ovnmmawr/external/aspect_rules_py+/tools/release/defs.bzl:5:6: Unable to find package for @@[unknown repo 'rules_rust' requested from @@aspect_rules_py+]//rust:defs.bzl: The repository '@@[unknown repo 'rules_rust' requested from @@aspect_rules_py+]' could not be resolved: No repository visible as '@rules_rust' from repository '@@aspect_rules_py+'.
ERROR: D:/udu/b/ovnmmawr/external/aspect_rules_py+/py/private/toolchain/venv/BUILD.bazel:3:17: error loading package '@@aspect_rules_py+//py/tools/venv_bin': at D:/udu/b/ovnmmawr/external/aspect_rules_py+/tools/release/defs.bzl:5:6: Unable to find package for @@[unknown repo 'rules_rust' requested from @@aspect_rules_py+]//rust:defs.bzl: The repository '@@[unknown repo 'rules_rust' requested from @@aspect_rules_py+]' could not be resolved: No repository visible as '@rules_rust' from repository '@@aspect_rules_py+'. and referenced by '@@aspect_rules_py+//py/private/toolchain/venv:venv_toolchain_source'
ERROR: Analysis of target '//:venv' failed; build aborted: Analysis failed

Without py_venv in my BUILD.bazel:

>bazel test //...
INFO: Invocation ID: 4de2c04c-321a-4e43-a3e0-44348f85ba2f
ERROR: error loading package '@@aspect_rules_py+//py/tools/venv_bin': at D:/udu/b/ovnmmawr/external/aspect_rules_py+/tools/release/defs.bzl:5:6: Unable to find package for @@[unknown repo 'rules_rust' requested from @@aspect_rules_py+]//rust:defs.bzl: The repository '@@[unknown repo 'rules_rust' requested from @@aspect_rules_py+]' could not be resolved: No repository visible as '@rules_rust' from repository '@@aspect_rules_py+'.
ERROR: D:/udu/b/ovnmmawr/external/aspect_rules_py+/py/private/toolchain/venv/BUILD.bazel:3:17: error loading package '@@aspect_rules_py+//py/tools/venv_bin': at D:/udu/b/ovnmmawr/external/aspect_rules_py+/tools/release/defs.bzl:5:6: Unable to find package for @@[unknown repo 'rules_rust' requested from @@aspect_rules_py+]//rust:defs.bzl: The repository '@@[unknown repo 'rules_rust' requested from @@aspect_rules_py+]' could not be resolved: No repository visible as '@rules_rust' from repository '@@aspect_rules_py+'. and referenced by '@@aspect_rules_py+//py/private/toolchain/venv:venv_toolchain_source

This is also reported via #566 in some messages after it was closed; creating a new issue for visibility.

Version

Development (host) and target OS/architectures:

Output of bazel --version:

Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file:

Language(s) and/or frameworks involved:

How to reproduce

Any other information?

No response

[arrdem]

Hey Chris, we don't (yet) ship prebuilds for windows, and we strip our release artifacts of the dev dependencies required to perform a source build of the normally prebuilt Rust tools so that we aren't imposing a very slow Rust and LLVM dependency on users.

The fix here would be to either 1) take a source dep (I'd suggest a git or http_archive override) on rules_py so that you do get the Rust deps and can try to do source builds or 2) help us ship Rust prebuilds for Windows.

Even if you got that going I'd be concerned that we have POSIX path assumptions throughout the codebase which may not shake and bake.

As it stands not really a bug, we don't have Windows support.

[arrdem]

Dupe of #9.

[arrdem]

Your previous work #622 and #618 dovetail here. The former we may be able to salvage some bits from. I do think that trying to replace rattler with uv and then revisiting the new venv building machinery to use windows friendly links is reasonable.