fix(pypi): propagate fails if overrides are passed only one index is used (#3666)

Before this PR there would be confusing failures when downloader config
is set to disallow certain values or when the authentication is not
setup properly. This is a small fix towards a better goal state where
we set `allow_fail = False` in cases where we know that we have to
succeed to download metadata from that particular URL.

The use-cases covered:
- Only one index_url is passed to `pip.parse`.
- `index_url_overrides` are passed which means that we should fail if
  there are insufficient overrides.

The downside to this is that it is really hard to return custom error
messages telling the user what to do, but on the flip side, the failures
coming from bazel itself might be more descriptive in the case of
outh-misconfiguration or bazel downloader configuration settings.

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