Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

unable to override https://pypi.org/simple starting in rules_python 2.0.0

オープン
#4,123 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
52/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
python
領域
build-system

調査の方向性

python/extensions:pip.bzl と pip.default.index_url および pip.parse のエントリポイントから始め、次に bazel clean --expunge に続けて bazel mod graph を実行して失敗を再現します。envsubst と設定された https://pypi.org/simple URL に焦点を当てて、rules_python 1.9.1 と 2.3.2 を比較します。設定されたインデックスが PyPI を上書きするか、非推奨のパラメータが明確な診断を生成すれば完了です。

索引モデルが issue の本文から書いたものです。

説明

🐞 bug report

Affected Rule
The issue is caused by the rule:

pip.parse.experimental_index_url
pip.parse.experimental_extra_index_urls
pip.default.index_url

Is this a regression?
Yes, the previous version in which this bug was not present was: 1.9.1
Description

In rules_python 1.9.1 and earlier, I was able to override the use of https://pypi.org/simple as follows:

pip.parse(
    envsubst = ["EXAMPLE_PIP_INDEX_URL"],
    experimental_extra_index_urls = [
        "${EXAMPLE_PIP_INDEX_URL}",
    ],
    experimental_index_url = "${EXAMPLE_PIP_INDEX_URL}",
    ...
)

where EXAMPLE_PIP_INDEX_URL is an environment variable that we set to our local pypi index.
We also have a --downloader_config set up which blocks access to pypi.org.

Starting with rules_python 2.0.0 and continuing through 2.3.2, the experimental_extra_index_urls and experimental_index_url parameters silently no longer work, and do not generate any diagnostic to say what the new mechanism is.

Per the documentation at https://rules-python.readthedocs.io/en/2.3.2/api/rules_python/python/extensions/pip.html#pip.default.index_url I would expect the following to work starting with rules_python 2.0.0:

pip.default(
    index_url = "${EXAMPLE_PIP_INDEX_URL}",
)
pip.parse(
    envsubst = ["EXAMPLE_PIP_INDEX_URL"],
    ...
)

However, it appears that index_url is not used at all, or at least does not override all uses of https://pypi.org/simple. The docs state that

This value is going to be subject to envsubst substitutions if necessary

I do need it to be subject to envsubst substitutions. It would be clearer if the docs said

This value is subject to envsubst substitutions

🔬 Minimal Reproduction

I can provide a small reproduction if necessary, but the user would need to supply some alternative to pypi.org to configure it with.

🔥 Exception or Error

When I run bazel clean --expunge; bazel mod graph in a repo configured as I described above, I get a diagnostic like

    Error in wait: java.io.IOException: Configured URL rewriter blocked all URLs: [https://pypi.org/simple/]
    ERROR: error evaluating module extension @@rules_python+//python/extensions:pip.bzl%pip
    ERROR: Results may be incomplete as 1 extension failed.

starting with rules_python 2.0.0 due to pypi.org/simple not being overridden any more, either by the old mechanism with experimental_index_url and experimental_extra_index_urls, or by the new mechanism with index_url.

🌍 Your Environment

Operating System:

Ubuntu 24.04

Output of bazel version:

  
$ bazelisk version
Bazelisk version: v1.19.0
Build label: 9.2.0
Build target: @@//src/main/java/com/google/devtools/build/lib/bazel:BazelServer
Build time: Mon Jul 13 18:15:04 2026 (1783966504)
Build timestamp: 1783966504
Build timestamp as int: 1783966504
  

Rules_python version:

  
2.3.2
  

Anything else relevant?

I'd be happy to attempt a fix, given some guidance as to what needed to be done where.
I'm also happy to test prospective fixes if my particular computing environment can be of some help.

It would be nice if experimental_extra_index_urls and experimental_index_url continued to work. But if they are not going to work, their use should at a minimum trigger some sort of clear diagnostic about what to use instead.

Posted on the bazel slack at https://bazelbuild.slack.com/archives/CA306CEV6/p1787963436682509

主要言語
Starlark
スター
690
フォーク
722
平均マージ
1日 55分
マージ済み PR(30日)
38

コントリビューションガイド

コントリビューションガイドを開く

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

bazel-contrib/rules_python のほかの issue

bazel-contrib/rules_python の issue をすべて見る

似ている issue

Build System の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。