Google Git
Sign in
pigweed / third_party / github / bazelbuild / rules_python / 45821b8603cd8b1f0791322de1c223bf5713c24d
commit45821b8603cd8b1f0791322de1c223bf5713c24d[log] [tgz]
authorIgnas Anikevicius <240938+aignas@users.noreply.github.com>Tue Nov 25 08:51:39 2025 +0900
committerGitHub <noreply@github.com>Mon Nov 24 23:51:39 2025 +0000
tree79b4843474fdd25778d9c73f32b1b4ea7cdd7c11
parenta9056b1ff23063f4605d77acc3aa362cbd6103d1 [diff]
fix(pip): do not add a pip-fallback when there is no sdist (#3432)

Before this PR the user would have to specify `download = True` in order
to not
fallback to pip, which is admittedly an odd interface design. With this
PR we
correctly do not add a `pip` fallback if there is no `sdist` to be used.
With
this in place we are better placed to enable the
`experimental_index_url` by
default. What is more we can more reliably detect when we should use a
special
repository rule to prepare for building from sdist.

Summary:
- Add a test that shows the problem and then adjust the torch
experimental URL
  test.
- Cleanup unused marker stubs in the tests.
- Fix the code to better handle the case when there is no sdist.

Work towards #260
Work towards #2410
2 files changed
tree: 79b4843474fdd25778d9c73f32b1b4ea7cdd7c11
  1. .bazelci/
  2. .bcr/
  3. .ci/
  4. .github/
  5. docs/
  6. examples/
  7. gazelle/
  8. private/
  9. python/
  10. sphinxdocs/
  11. tests/
  12. tools/
  13. .bazelignore
  14. .bazelrc
  15. .bazelrc.deleted_packages
  16. .bazelversion
  17. .editorconfig
  18. .git-blame-ignore-revs
  19. .gitattributes
  20. .gitignore
  21. .pre-commit-config.yaml
  22. .python-version
  23. .readthedocs.yml
  24. addlicense.sh
  25. AGENTS.md
  26. AUTHORS
  27. BUILD.bazel
  28. BZLMOD_SUPPORT.md
  29. CHANGELOG.md
  30. CONTRIBUTING.md
  31. CONTRIBUTORS
  32. GEMINI.md
  33. internal_dev_deps.bzl
  34. internal_dev_setup.bzl
  35. LICENSE
  36. MODULE.bazel
  37. README.md
  38. RELEASING.md
  39. version.bzl
  40. WORKSPACE
  41. WORKSPACE.bzlmod
README.md

Python Rules for Bazel

Build status

Overview

This repository is the home of the core Python rules -- py_library, py_binary, py_test, py_proto_library, and related symbols that provide the basis for Python support in Bazel. It also contains package installation rules for integrating with PyPI and other indices.

Documentation for rules_python is at https://rules-python.readthedocs.io and in the Bazel Build Encyclopedia.

Examples live in the examples directory.

The core rules are stable. Their implementation is subject to Bazel's backward compatibility policy. This repository aims to follow semantic versioning.

The Bazel community maintains this repository. Neither Google nor the Bazel team provides support for the code. However, this repository is part of the test suite used to vet new Bazel releases. See How to contribute page for information on our development workflow.

Documentation

For detailed documentation, see https://rules-python.readthedocs.io

Bzlmod support

See Bzlmod support for more details.