chore: replace bazelbuild with bazel-contrib (#2688)
This was done using `grep | xargs sed`.
BCR presubmits require that the list of repositories match where
downloads come from
Along the way, also update the URL homepages to bazel-contrib and change
the email
to my personal instead of work email.
diff --git a/.bcr/gazelle/metadata.template.json b/.bcr/gazelle/metadata.template.json
index 687f78e..017f9d3 100644
--- a/.bcr/gazelle/metadata.template.json
+++ b/.bcr/gazelle/metadata.template.json
@@ -1,9 +1,9 @@
{
- "homepage": "https://github.com/bazelbuild/rules_python",
+ "homepage": "https://github.com/bazel-contrib/rules_python",
"maintainers": [
{
"name": "Richard Levasseur",
- "email": "rlevasseur@google.com",
+ "email": "richardlev@gmail.com",
"github": "rickeylev"
},
{
@@ -13,7 +13,8 @@
}
],
"repository": [
- "github:bazelbuild/rules_python"
+ "github:bazelbuild/rules_python",
+ "github:bazel-contrib/rules_python"
],
"versions": [],
"yanked_versions": {}
diff --git a/.bcr/metadata.template.json b/.bcr/metadata.template.json
index 579d688..9d85e22 100644
--- a/.bcr/metadata.template.json
+++ b/.bcr/metadata.template.json
@@ -1,9 +1,9 @@
{
- "homepage": "https://github.com/bazelbuild/rules_python",
+ "homepage": "https://github.com/bazel-contrib/rules_python",
"maintainers": [
{
"name": "Richard Levasseur",
- "email": "rlevasseur@google.com",
+ "email": "richardlev@gmail.com",
"github": "rickeylev"
},
{
diff --git a/.github/workflows/create_archive_and_notes.sh b/.github/workflows/create_archive_and_notes.sh
index 26091a8..a21585f 100755
--- a/.github/workflows/create_archive_and_notes.sh
+++ b/.github/workflows/create_archive_and_notes.sh
@@ -72,7 +72,7 @@
name = "rules_python",
sha256 = "${SHA}",
strip_prefix = "${PREFIX}",
- url = "https://github.com/bazelbuild/rules_python/releases/download/${TAG}/rules_python-${TAG}.tar.gz",
+ url = "https://github.com/bazel-contrib/rules_python/releases/download/${TAG}/rules_python-${TAG}.tar.gz",
)
load("@rules_python//python:repositories.bzl", "py_repositories")
@@ -90,7 +90,7 @@
name = "rules_python_gazelle_plugin",
sha256 = "${SHA}",
strip_prefix = "${PREFIX}/gazelle",
- url = "https://github.com/bazelbuild/rules_python/releases/download/${TAG}/rules_python-${TAG}.tar.gz",
+ url = "https://github.com/bazel-contrib/rules_python/releases/download/${TAG}/rules_python-${TAG}.tar.gz",
)
# To compile the rules_python gazelle extension from source,
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
index 29b70cc..436797e 100644
--- a/.github/workflows/release.yml
+++ b/.github/workflows/release.yml
@@ -33,7 +33,7 @@
# This special value tells pypi that the user identity is supplied within the token
TWINE_USERNAME: __token__
# Note, the PYPI_API_TOKEN is for the rules-python pypi user, added by @rickylev on
- # https://github.com/bazelbuild/rules_python/settings/secrets/actions
+ # https://github.com/bazel-contrib/rules_python/settings/secrets/actions
TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
run: bazel run --stamp --embed_label=${{ github.ref_name }} //python/runfiles:wheel.publish
- name: Release
diff --git a/BZLMOD_SUPPORT.md b/BZLMOD_SUPPORT.md
index 85e28ac..73fde46 100644
--- a/BZLMOD_SUPPORT.md
+++ b/BZLMOD_SUPPORT.md
@@ -11,7 +11,7 @@
## Configuration
-The releases page will give you the latest version number, and a basic example. The release page is located [here](/bazelbuild/rules_python/releases).
+The releases page will give you the latest version number, and a basic example. The release page is located [here](/bazel-contrib/rules_python/releases).
## What is bzlmod?
@@ -53,7 +53,7 @@
the toolchains rules_python registers**.
NOTE: Regardless of your toolchain, due to
-[#691](https://github.com/bazelbuild/rules_python/issues/691), `rules_python`
+[#691](https://github.com/bazel-contrib/rules_python/issues/691), `rules_python`
still relies on a local Python being available to bootstrap the program before
handing over execution to the toolchain Python.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 4e5f102..dc40a25 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -26,7 +26,7 @@
{#v0-0-0}
## Unreleased
-[0.0.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.0.0
+[0.0.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.0.0
{#v0-0-0-changed}
### Changed
@@ -49,7 +49,7 @@
{#v0-0-0}
## Unreleased
-[0.0.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.0.0
+[0.0.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.0.0
{#v0-0-0-changed}
### Changed
@@ -71,7 +71,7 @@
{#v1-3-0}
## Unreleased
-[1.3.0]: https://github.com/bazelbuild/rules_python/releases/tag/1.3.0
+[1.3.0]: https://github.com/bazel-contrib/rules_python/releases/tag/1.3.0
{#v1-3-0-changed}
### Changed
@@ -80,17 +80,17 @@
* (py_package) Package `py_library.pyi_srcs` (`.pyi` files) in `py_package`.
* (gazelle) The generated manifest file (default: `gazelle_python.yaml`) will now include the
YAML document start `---` line. Implemented in
- [#2656](https://github.com/bazelbuild/rules_python/pull/2656).
+ [#2656](https://github.com/bazel-contrib/rules_python/pull/2656).
{#v1-3-0-fixed}
### Fixed
* (pypi) The `ppc64le` is now pointing to the right target in the `platforms` package.
* (gazelle) No longer incorrectly merge `py_binary` targets during partial updates in
- `file` generation mode. Fixed in [#2619](https://github.com/bazelbuild/rules_python/pull/2619).
+ `file` generation mode. Fixed in [#2619](https://github.com/bazel-contrib/rules_python/pull/2619).
* (bzlmod) Running as root is no longer an error. `ignore_root_user_error=True`
is now the default. Note that running as root may still cause spurious
Bazel cache invalidation
- ([#1169](https://github.com/bazelbuild/rules_python/issues/1169)).
+ ([#1169](https://github.com/bazel-contrib/rules_python/issues/1169)).
* (gazelle) Don't collapse depsets to a list or into args when generating the modules mapping file.
Support spilling modules mapping args into a params file.
* (coverage) Fix missing files in the coverage report if they have no tests.
@@ -113,10 +113,10 @@
building wheels from `sdist`.
* (pypi) Direct HTTP urls for wheels and sdists are now supported when using
{obj}`experimental_index_url` (bazel downloader).
- Partially fixes [#2363](https://github.com/bazelbuild/rules_python/issues/2363).
+ Partially fixes [#2363](https://github.com/bazel-contrib/rules_python/issues/2363).
* (rules) APIs for creating custom rules based on the core py_binary, py_test,
and py_library rules
- ([#1647](https://github.com/bazelbuild/rules_python/issues/1647))
+ ([#1647](https://github.com/bazel-contrib/rules_python/issues/1647))
* (rules) Added env-var to allow additional interpreter args for stage1 bootstrap.
See {obj}`RULES_PYTHON_ADDITIONAL_INTERPRETER_ARGS` environment variable.
Only applicable for {obj}`--bootstrap_impl=script`.
@@ -132,7 +132,7 @@
{#v1-2-0}
## [1.2.0] - 2025-02-21
-[1.2.0]: https://github.com/bazelbuild/rules_python/releases/tag/1.2.0
+[1.2.0]: https://github.com/bazel-contrib/rules_python/releases/tag/1.2.0
{#v1-2-0-changed}
### Changed
@@ -140,7 +140,7 @@
implementation in https://github.com/protocolbuffers/protobuf. It will be
removed in the future release.
* (pypi) {obj}`pip.override` will now be ignored instead of raising an error,
- fixes [#2550](https://github.com/bazelbuild/rules_python/issues/2550).
+ fixes [#2550](https://github.com/bazel-contrib/rules_python/issues/2550).
* (rules) deprecation warnings for deprecated symbols have been turned off by
default for now and can be enabled with `RULES_PYTHON_DEPRECATION_WARNINGS`
env var.
@@ -150,24 +150,24 @@
{#v1-2-0-fixed}
### Fixed
* (rules) `python_zip_file` output with `--bootstrap_impl=script` works again
- ([#2596](https://github.com/bazelbuild/rules_python/issues/2596)).
+ ([#2596](https://github.com/bazel-contrib/rules_python/issues/2596)).
* (docs) Using `python_version` attribute for specifying python versions introduced in `v1.1.0`
* (gazelle) Providing multiple input requirements files to `gazelle_python_manifest` now works correctly.
* (pypi) Handle trailing slashes in pip index URLs in environment variables,
- fixes [#2554](https://github.com/bazelbuild/rules_python/issues/2554).
+ fixes [#2554](https://github.com/bazel-contrib/rules_python/issues/2554).
* (runfiles) Runfile manifest and repository mapping files are now interpreted
as UTF-8 on all platforms.
* (coverage) Coverage with `--bootstrap_impl=script` is fixed
- ([#2572](https://github.com/bazelbuild/rules_python/issues/2572)).
+ ([#2572](https://github.com/bazel-contrib/rules_python/issues/2572)).
* (pypi) Non deterministic behaviour in requirement file usage has been fixed
- by reverting [#2514](https://github.com/bazelbuild/rules_python/pull/2514).
- The related issue is [#908](https://github.com/bazelbuild/rules_python/issue/908).
+ by reverting [#2514](https://github.com/bazel-contrib/rules_python/pull/2514).
+ The related issue is [#908](https://github.com/bazel-contrib/rules_python/issue/908).
* (sphinxdocs) Do not crash when `tag_class` does not have a populated `doc` value.
- Fixes ([#2579](https://github.com/bazelbuild/rules_python/issues/2579)).
+ Fixes ([#2579](https://github.com/bazel-contrib/rules_python/issues/2579)).
* (binaries/tests) Fix packaging when using `--bootstrap_impl=script`: set
{obj}`--venvs_use_declare_symlink=no` to have it not create symlinks at
build time (they will be created at runtime instead).
- (Fixes [#2489](https://github.com/bazelbuild/rules_python/issues/2489))
+ (Fixes [#2489](https://github.com/bazel-contrib/rules_python/issues/2489))
{#v1-2-0-added}
### Added
@@ -180,7 +180,7 @@
{#v1-1-0}
## [1.1.0] - 2025-01-07
-[1.1.0]: https://github.com/bazelbuild/rules_python/releases/tag/1.1.0
+[1.1.0]: https://github.com/bazel-contrib/rules_python/releases/tag/1.1.0
{#v1-1-0-changed}
### Changed
@@ -213,7 +213,7 @@
marker information allowing `bazel query` to work in cases where the `whl` is
available for all of the platforms and the sdist can be built. This fix is
for both WORKSPACE and `bzlmod` setups.
- Fixes [#2450](https://github.com/bazelbuild/rules_python/issues/2450).
+ Fixes [#2450](https://github.com/bazel-contrib/rules_python/issues/2450).
* (gazelle) Gazelle will now correctly parse Python3.12 files that use [PEP 695 Type
Parameter Syntax][pep-695]. (#2396)
* (pypi) Using {bzl:obj}`pip_parse.experimental_requirement_cycles` and
@@ -221,16 +221,16 @@
using WORKSPACE files.
* (pypi) The error messages when the wheel distributions do not match anything
are now printing more details and include the currently active flag
- values. Fixes [#2466](https://github.com/bazelbuild/rules_python/issues/2466).
+ values. Fixes [#2466](https://github.com/bazel-contrib/rules_python/issues/2466).
* (py_proto_library) Fix import paths in Bazel 8.
* (whl_library) Now the changes to the dependencies are correctly tracked when
PyPI packages used in {bzl:obj}`whl_library` during the `repository_rule` phase
- change. Fixes [#2468](https://github.com/bazelbuild/rules_python/issues/2468).
+ change. Fixes [#2468](https://github.com/bazel-contrib/rules_python/issues/2468).
+ (gazelle) Gazelle no longer ignores `setup.py` files by default. To restore
this behavior, apply the `# gazelle:python_ignore_files setup.py` directive.
* Don't re-fetch whl_library, python_repository, etc. repository rules
whenever `PATH` changes. Fixes
- [#2551](https://github.com/bazelbuild/rules_python/issues/2551).
+ [#2551](https://github.com/bazel-contrib/rules_python/issues/2551).
[pep-695]: https://peps.python.org/pep-0695/
@@ -244,7 +244,7 @@
{obj}`experimental_index_url` usage or the regular `pip.parse` usage.
To select the free-threaded interpreter in the repo phase, please use
the documented [env](/environment-variables.html) variables.
- Fixes [#2386](https://github.com/bazelbuild/rules_python/issues/2386).
+ Fixes [#2386](https://github.com/bazel-contrib/rules_python/issues/2386).
* (toolchains) Use the latest astrahl-sh toolchain release [20241206] for Python versions:
* 3.9.21
* 3.10.16
@@ -269,7 +269,7 @@
{#v1-0-0}
## [1.0.0] - 2024-12-05
-[1.0.0]: https://github.com/bazelbuild/rules_python/releases/tag/1.0.0
+[1.0.0]: https://github.com/bazel-contrib/rules_python/releases/tag/1.0.0
{#v1-0-0-changed}
### Changed
@@ -308,12 +308,12 @@
* (toolchains) stop depending on `uname` to get the value of the host platform.
* (pypi): Correctly handle multiple versions of the same package in the requirements
files which is useful when including different PyTorch builds (e.g. <pytorch+cpu> vs <pytorch+cu118> ) for different target platforms.
- Fixes ([2337](https://github.com/bazelbuild/rules_python/issues/2337)).
+ Fixes ([2337](https://github.com/bazel-contrib/rules_python/issues/2337)).
* (uv): Correct the sha256sum for the `uv` binary for aarch64-apple-darwin.
- Fixes ([2411](https://github.com/bazelbuild/rules_python/issues/2411)).
+ Fixes ([2411](https://github.com/bazel-contrib/rules_python/issues/2411)).
* (binaries/tests) ({obj}`--bootstrap_impl=scipt`) Using `sys.executable` will
use the same `sys.path` setup as the calling binary.
- ([2169](https://github.com/bazelbuild/rules_python/issues/2169)).
+ ([2169](https://github.com/bazel-contrib/rules_python/issues/2169)).
* (workspace) Corrected protobuf's name to com_google_protobuf, the name is
hardcoded in Bazel, WORKSPACE mode.
* (pypi): {bzl:obj}`compile_pip_requirements` no longer fails on Windows when `--enable_runfiles` is not enabled.
@@ -352,7 +352,7 @@
{#v0-40-0}
## [0.40.0] - 2024-11-17
-[0.40.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.40.0
+[0.40.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.40.0
{#v0-40-changed}
### Changed
@@ -361,7 +361,7 @@
{#v0-40-fixed}
### Fixed
* (rules) Don't drop custom import paths if Bazel-builtin PyInfo is removed.
- ([2414](https://github.com/bazelbuild/rules_python/issues/2414)).
+ ([2414](https://github.com/bazel-contrib/rules_python/issues/2414)).
{#v0-40-added}
### Added
@@ -380,7 +380,7 @@
{#v0-39-0}
## [0.39.0] - 2024-11-13
-[0.39.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.39.0
+[0.39.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.39.0
{#v0-39-0-changed}
### Changed
@@ -408,7 +408,7 @@
### Fixed
* (precompiling) Skip precompiling (instead of erroring) if the legacy
`@bazel_tools//tools/python:autodetecting_toolchain` is being used
- ([#2364](https://github.com/bazelbuild/rules_python/issues/2364)).
+ ([#2364](https://github.com/bazel-contrib/rules_python/issues/2364)).
{#v0-39-0-added}
### Added
@@ -426,14 +426,14 @@
{#v0-38-0}
## [0.38.0] - 2024-11-08
-[0.38.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.38.0
+[0.38.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.38.0
{#v0-38-0-changed}
### Changed
* (deps) (WORKSPACE only) rules_cc 0.0.13 and protobuf 27.0 is now the default
version used; this for Bazel 8+ support (previously version was rules_cc 0.0.9
and no protobuf version specified)
- ([2310](https://github.com/bazelbuild/rules_python/issues/2310)).
+ ([2310](https://github.com/bazel-contrib/rules_python/issues/2310)).
* (publish) The dependencies have been updated to the latest available versions
for the `twine` publishing rule.
* (whl_library) Remove `--no-build-isolation` to allow non-hermetic sdist builds
@@ -452,7 +452,7 @@
{#v0-38-0-fixed}
### Fixed
* (pypi) (Bazel 7.4+) Allow spaces in filenames included in `whl_library`s
- ([617](https://github.com/bazelbuild/rules_python/issues/617)).
+ ([617](https://github.com/bazel-contrib/rules_python/issues/617)).
* (pypi) When {attr}`pip.parse.experimental_index_url` is set, we need to still
pass the `extra_pip_args` value when building an `sdist`.
* (pypi) The patched wheel filenames from now on are using local version specifiers
@@ -462,7 +462,7 @@
or not. To opt into this behavior, set
`pip.parse.parse_all_requirements_files`, which will become the
default in future releases leading up to `1.0.0`. Fixes
- [#2268](https://github.com/bazelbuild/rules_python/issues/2268). A known
+ [#2268](https://github.com/bazel-contrib/rules_python/issues/2268). A known
issue is that it may break `bazel query` and in these use cases it is
advisable to use `cquery` or switch to `download_only = True`
@@ -476,7 +476,7 @@
* The rules_python version is now reported in `//python/features.bzl#features.version`
* (pip.parse) {attr}`pip.parse.extra_hub_aliases` can now be used to expose extra
targets created by annotations in whl repositories.
- Fixes [#2187](https://github.com/bazelbuild/rules_python/issues/2187).
+ Fixes [#2187](https://github.com/bazel-contrib/rules_python/issues/2187).
* (bzlmod) `pip.parse` now supports `whl-only` setup using
`download_only = True` where users can specify multiple requirements files
and use the `pip` backend to do the downloading. This was only available for
@@ -486,7 +486,7 @@
{#v0-37-2}
## [0.37.2] - 2024-10-27
-[0.37.2]: https://github.com/bazelbuild/rules_python/releases/tag/0.37.2
+[0.37.2]: https://github.com/bazel-contrib/rules_python/releases/tag/0.37.2
{#v0-37-2-fixed}
### Fixed
@@ -497,18 +497,18 @@
{#v0-37-1}
## [0.37.1] - 2024-10-22
-[0.37.1]: https://github.com/bazelbuild/rules_python/releases/tag/0.37.1
+[0.37.1]: https://github.com/bazel-contrib/rules_python/releases/tag/0.37.1
{#v0-37-1-fixed}
### Fixed
* (rules) Setting `--incompatible_python_disallow_native_rules` no longer
causes rules_python rules to fail
- ([#2326](https://github.com/bazelbuild/rules_python/issues/2326)).
+ ([#2326](https://github.com/bazel-contrib/rules_python/issues/2326)).
{#v0-37-0}
## [0.37.0] - 2024-10-18
-[0.37.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.37.0
+[0.37.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.37.0
{#v0-37-0-changed}
### Changed
@@ -538,7 +538,7 @@
way to {obj}`whl_library`. What is more we will pass the `extra_pip_args` to
{obj}`whl_library` for `sdist` distributions when using
{attr}`pip.parse.experimental_index_url`. See
- [#2239](https://github.com/bazelbuild/rules_python/issues/2239).
+ [#2239](https://github.com/bazel-contrib/rules_python/issues/2239).
* (whl_filegroup): Provide per default also the `RECORD` file
* (py_wheel): `RECORD` file entry elements are now quoted if necessary when a
wheel is created
@@ -546,17 +546,17 @@
case where a requirement has many `--hash=sha256:...` flags
* (rules) `compile_pip_requirements` passes `env` to the `X.update` target (and
not only to the `X_test` target, a bug introduced in
- [#1067](https://github.com/bazelbuild/rules_python/pull/1067)).
+ [#1067](https://github.com/bazel-contrib/rules_python/pull/1067)).
* (bzlmod) In hybrid bzlmod with WORKSPACE builds,
`python_register_toolchains(register_toolchains=True)` is respected
- ([#1675](https://github.com/bazelbuild/rules_python/issues/1675)).
+ ([#1675](https://github.com/bazel-contrib/rules_python/issues/1675)).
* (precompiling) The {obj}`pyc_collection` attribute now correctly
enables (or disables) using pyc files from targets transitively
* (pip) Skip patching wheels not matching `pip.override`'s `file`
- ([#2294](https://github.com/bazelbuild/rules_python/pull/2294)).
+ ([#2294](https://github.com/bazel-contrib/rules_python/pull/2294)).
* (chore): Add a `rules_shell` dev dependency and moved a `sh_test` target
outside of the `//:BUILD.bazel` file.
- Fixes [#2299](https://github.com/bazelbuild/rules_python/issues/2299).
+ Fixes [#2299](https://github.com/bazel-contrib/rules_python/issues/2299).
{#v0-37-0-added}
### Added
@@ -593,7 +593,7 @@
{#v0-36-0}
## [0.36.0] - 2024-09-24
-[0.36.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.36.0
+[0.36.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.36.0
{#v0-36-0-changed}
### Changed
@@ -632,7 +632,7 @@
* (rules) Make `RUNFILES_MANIFEST_FILE`-based invocations work when used with
{obj}`--bootstrap_impl=script`. This fixes invocations using non-sandboxed
test execution with `--enable_runfiles=false --build_runfile_manifests=true`.
- ([#2186](https://github.com/bazelbuild/rules_python/issues/2186)).
+ ([#2186](https://github.com/bazel-contrib/rules_python/issues/2186)).
* (py_wheel) Fix incorrectly generated `Required-Dist` when specifying requirements with markers
in extra_requires in py_wheel rule.
* (rules) Prevent pytest from trying run the generated stage2
@@ -645,7 +645,7 @@
* (bzlmod): Toolchain overrides can now be done using the new
{bzl:obj}`python.override`, {bzl:obj}`python.single_version_override` and
{bzl:obj}`python.single_version_platform_override` tag classes.
- See [#2081](https://github.com/bazelbuild/rules_python/issues/2081).
+ See [#2081](https://github.com/bazel-contrib/rules_python/issues/2081).
* (rules) Executables provide {obj}`PyExecutableInfo`, which contains
executable-specific information useful for packaging an executable or
or deriving a new one from the original.
@@ -671,7 +671,7 @@
{#v0-35-0}
## [0.35.0] - 2024-08-15
-[0.35.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.35.0
+[0.35.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.35.0
{#v0-35-0-changed}
### Changed
@@ -685,7 +685,7 @@
* `3.12 -> 3.12.4`
* (rules) `PYTHONSAFEPATH` is inherited from the calling environment to allow
disabling it (Requires {obj}`--bootstrap_impl=script`)
- ([#2060](https://github.com/bazelbuild/rules_python/issues/2060)).
+ ([#2060](https://github.com/bazel-contrib/rules_python/issues/2060)).
{#v0-35-0-fixed}
### Fixed
@@ -699,42 +699,42 @@
execroot.
* (rules) Signals are properly received when using {obj}`--bootstrap_impl=script`
(for non-zip builds).
- ([#2043](https://github.com/bazelbuild/rules_python/issues/2043))
+ ([#2043](https://github.com/bazel-contrib/rules_python/issues/2043))
* (rules) Fixes Python builds when the `--build_python_zip` is set to `false` on
- Windows. See [#1840](https://github.com/bazelbuild/rules_python/issues/1840).
+ Windows. See [#1840](https://github.com/bazel-contrib/rules_python/issues/1840).
* (rules) Fixes Mac + `--build_python_zip` + {obj}`--bootstrap_impl=script`
- ([#2030](https://github.com/bazelbuild/rules_python/issues/2030)).
+ ([#2030](https://github.com/bazel-contrib/rules_python/issues/2030)).
* (rules) User dependencies come before runtime site-packages when using
{obj}`--bootstrap_impl=script`.
- ([#2064](https://github.com/bazelbuild/rules_python/issues/2064)).
+ ([#2064](https://github.com/bazel-contrib/rules_python/issues/2064)).
* (rules) Version-aware rules now return both `@_builtins` and `@rules_python`
providers instead of only one.
- ([#2114](https://github.com/bazelbuild/rules_python/issues/2114)).
+ ([#2114](https://github.com/bazel-contrib/rules_python/issues/2114)).
* (pip) Fixed pypi parse_simpleapi_html function for feeds with package metadata
containing ">" sign
* (toolchains) Added missing executable permission to
`//python/runtime_env_toolchains` interpreter script so that it is runnable.
- ([#2085](https://github.com/bazelbuild/rules_python/issues/2085)).
+ ([#2085](https://github.com/bazel-contrib/rules_python/issues/2085)).
* (pip) Correctly use the `sdist` downloaded by the bazel downloader when using
`experimental_index_url` feature. Fixes
- [#2091](https://github.com/bazelbuild/rules_python/issues/2090).
+ [#2091](https://github.com/bazel-contrib/rules_python/issues/2090).
* (gazelle) Make `gazelle_python_manifest.update` manual to avoid unnecessary
network behavior.
* (bzlmod): The conflicting toolchains during `python` extension will no longer
cause warnings by default. In order to see the warnings for diagnostic purposes
set the env var `RULES_PYTHON_REPO_DEBUG_VERBOSITY` to one of `INFO`, `DEBUG` or `TRACE`.
- Fixes [#1818](https://github.com/bazelbuild/rules_python/issues/1818).
+ Fixes [#1818](https://github.com/bazel-contrib/rules_python/issues/1818).
* (runfiles) Make runfiles lookups work for the situation of Bazel 7,
Python 3.9 (or earlier, where safepath isn't present), and the Rlocation call
in the same directory as the main file.
- Fixes [#1631](https://github.com/bazelbuild/rules_python/issues/1631).
+ Fixes [#1631](https://github.com/bazel-contrib/rules_python/issues/1631).
{#v0-35-0-added}
### Added
* (rules) `compile_pip_requirements` supports multiple requirements input files as `srcs`.
* (rules) `PYTHONSAFEPATH` is inherited from the calling environment to allow
disabling it (Requires {obj}`--bootstrap_impl=script`)
- ([#2060](https://github.com/bazelbuild/rules_python/issues/2060)).
+ ([#2060](https://github.com/bazel-contrib/rules_python/issues/2060)).
* (gazelle) Added `python_generation_mode_per_package_require_test_entry_point`
in order to better accommodate users who use a custom macro,
[`pytest-bazel`][pytest_bazel], [rules_python_pytest] or `rules_py`
@@ -756,7 +756,7 @@
{#v0-34-0}
## [0.34.0] - 2024-07-04
-[0.34.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.34.0
+[0.34.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.34.0
{#v0-34-0-changed}
### Changed
@@ -797,7 +797,7 @@
and drop the defaults from the lock file.
* (whl_library) Correctly handle arch-specific dependencies when we encounter a
platform specific wheel and use `experimental_target_platforms`.
- Fixes [#1996](https://github.com/bazelbuild/rules_python/issues/1996).
+ Fixes [#1996](https://github.com/bazel-contrib/rules_python/issues/1996).
* (rules) The first element of the default outputs is now the executable again.
* (pip) Fixed crash when pypi packages lacked a sha (e.g. yanked packages)
@@ -807,7 +807,7 @@
replacement for the "autodetecting" toolchain.
* (gazelle) Added new `python_label_convention` and `python_label_normalization` directives. These directive
allows altering default Gazelle label format to third-party dependencies useful for re-using Gazelle plugin
- with other rules, including `rules_pycross`. See [#1939](https://github.com/bazelbuild/rules_python/issues/1939).
+ with other rules, including `rules_pycross`. See [#1939](https://github.com/bazel-contrib/rules_python/issues/1939).
{#v0-34-0-removed}
### Removed
@@ -816,7 +816,7 @@
{#v0-33-2}
## [0.33.2] - 2024-06-13
-[0.33.2]: https://github.com/bazelbuild/rules_python/releases/tag/0.33.2
+[0.33.2]: https://github.com/bazel-contrib/rules_python/releases/tag/0.33.2
{#v0-33-2-fixed}
### Fixed
@@ -824,22 +824,22 @@
To enable it, set {obj}`--//python/config_settings:exec_tools_toolchain=enabled`.
This toolchain must be enabled for precompilation to work. This toolchain will
be enabled by default in a future release.
- Fixes [#1967](https://github.com/bazelbuild/rules_python/issues/1967).
+ Fixes [#1967](https://github.com/bazel-contrib/rules_python/issues/1967).
{#v0-33-1}
## [0.33.1] - 2024-06-13
-[0.33.1]: https://github.com/bazelbuild/rules_python/releases/tag/0.33.1
+[0.33.1]: https://github.com/bazel-contrib/rules_python/releases/tag/0.33.1
{#v0-33-1-fixed}
### Fixed
* (py_binary) Fix building of zip file when using `--build_python_zip`
- argument. Fixes [#1954](https://github.com/bazelbuild/rules_python/issues/1954).
+ argument. Fixes [#1954](https://github.com/bazel-contrib/rules_python/issues/1954).
{#v0-33-0}
## [0.33.0] - 2024-06-12
-[0.33.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.33.0
+[0.33.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.33.0
{#v0-33-0-changed}
### Changed
@@ -859,8 +859,8 @@
* (pip.parse): Add references to all supported wheels when using `experimental_index_url`
to allowing to correctly fetch the wheels for the right platform. See the
updated docs on how to use the feature. This is work towards addressing
- [#735](https://github.com/bazelbuild/rules_python/issues/735) and
- [#260](https://github.com/bazelbuild/rules_python/issues/260). The spoke
+ [#735](https://github.com/bazel-contrib/rules_python/issues/735) and
+ [#260](https://github.com/bazel-contrib/rules_python/issues/260). The spoke
repository names when using this flag will have a structure of
`{pip_hub_prefix}_{wheel_name}_{py_tag}_{abi_tag}_{platform_tag}_{sha256}`,
which is an implementation detail which should not be relied on and is there
@@ -886,13 +886,13 @@
* (bzlmod) remove `pip.parse(annotations)` attribute as it is unused and has been
replaced by whl_modifications.
* (pip) Correctly select wheels when the python tag includes minor versions.
- See ([#1930](https://github.com/bazelbuild/rules_python/issues/1930))
+ See ([#1930](https://github.com/bazel-contrib/rules_python/issues/1930))
* (pip.parse): The lock file is now reproducible on any host platform if the
`experimental_index_url` is not used by any of the modules in the dependency
chain. To make the lock file identical on each `os` and `arch`, please use
the `experimental_index_url` feature which will fetch metadata from PyPI or a
different private index and write the contents to the lock file. Fixes
- [#1643](https://github.com/bazelbuild/rules_python/issues/1643).
+ [#1643](https://github.com/bazel-contrib/rules_python/issues/1643).
* (pip.parse): Install `yanked` packages and print a warning instead of
ignoring them. This better matches the behaviour of `uv pip install`.
* (toolchains): Now matching of the default hermetic toolchain is more robust
@@ -901,7 +901,7 @@
to toolchain selection failures when the python toolchain is not registered,
but is requested via `//python/config_settings:python_version` flag setting.
* (doc) Fix the `WORKSPACE` requirement vendoring example. Fixes
- [#1918](https://github.com/bazelbuild/rules_python/issues/1918).
+ [#1918](https://github.com/bazel-contrib/rules_python/issues/1918).
{#v0-33-0-added}
### Added
@@ -912,7 +912,7 @@
[Precompiling docs][precompile-docs] and API reference docs for more
information on precompiling. Note this requires Bazel 7+ and the Pystar rule
implementation enabled.
- ([#1761](https://github.com/bazelbuild/rules_python/issues/1761))
+ ([#1761](https://github.com/bazel-contrib/rules_python/issues/1761))
* (rules) Attributes and flags to control precompile behavior: `precompile`,
`precompile_optimize_level`, `precompile_source_retention`,
`precompile_invalidation_mode`, and `pyc_collection`
@@ -938,7 +938,7 @@
is available. It can be enabled by setting
{obj}`--@rules_python//python/config_settings:bootstrap_impl=script`. It
will become the default in a subsequent release.
- ([#691](https://github.com/bazelbuild/rules_python/issues/691))
+ ([#691](https://github.com/bazel-contrib/rules_python/issues/691))
* (providers) `PyRuntimeInfo` has two new attributes:
{obj}`PyRuntimeInfo.stage2_bootstrap_template` and
{obj}`PyRuntimeInfo.zip_main_template`.
@@ -960,7 +960,7 @@
{#v0-32-2}
## [0.32.2] - 2024-05-14
-[0.32.2]: https://github.com/bazelbuild/rules_python/releases/tag/0.32.2
+[0.32.2]: https://github.com/bazel-contrib/rules_python/releases/tag/0.32.2
{#v0-32-2-fixed}
### Fixed
@@ -968,12 +968,12 @@
* Workaround existence of infinite symlink loops on case insensitive filesystems when targeting linux platforms with recent Python toolchains. Works around an upstream [issue][indygreg-231]. Fixes [#1800][rules_python_1800].
[indygreg-231]: https://github.com/indygreg/python-build-standalone/issues/231
-[rules_python_1800]: https://github.com/bazelbuild/rules_python/issues/1800
+[rules_python_1800]: https://github.com/bazel-contrib/rules_python/issues/1800
{#v0-32-0}
## [0.32.0] - 2024-05-12
-[0.32.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.32.0
+[0.32.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.32.0
{#v0-32-0-changed}
### Changed
@@ -998,22 +998,22 @@
* (whl_library): Fix the experimental_target_platforms overriding for platform
specific wheels when the wheels are for any python interpreter version. Fixes
- [#1810](https://github.com/bazelbuild/rules_python/issues/1810).
+ [#1810](https://github.com/bazel-contrib/rules_python/issues/1810).
* (whl_library): Stop generating duplicate dependencies when encountering
duplicates in the METADATA. Fixes
- [#1873](https://github.com/bazelbuild/rules_python/issues/1873).
+ [#1873](https://github.com/bazel-contrib/rules_python/issues/1873).
* (gazelle) In `project` or `package` generation modes, do not generate `py_test`
rules when there are no test files and do not set `main = "__test__.py"` when
that file doesn't exist.
* (whl_library) The group redirection is only added when the package is part of
the group potentially fixing aspects that want to traverse a `py_library` graph.
- Fixes [#1760](https://github.com/bazelbuild/rules_python/issues/1760).
+ Fixes [#1760](https://github.com/bazel-contrib/rules_python/issues/1760).
* (bzlmod) Setting a particular micro version for the interpreter and the
`pip.parse` extension is now possible, see the
`examples/pip_parse/MODULE.bazel` for how to do it.
- See [#1371](https://github.com/bazelbuild/rules_python/issues/1371).
+ See [#1371](https://github.com/bazel-contrib/rules_python/issues/1371).
* (refactor) The pre-commit developer workflow should now pass `isort` and `black`
- checks (see [#1674](https://github.com/bazelbuild/rules_python/issues/1674)).
+ checks (see [#1674](https://github.com/bazel-contrib/rules_python/issues/1674)).
### Added
@@ -1031,13 +1031,13 @@
[original issue][test_file_pattern_issue] and the [docs][test_file_pattern_docs]
for details.
* (wheel) Add support for `data_files` attributes in py_wheel rule
- ([#1777](https://github.com/bazelbuild/rules_python/issues/1777))
+ ([#1777](https://github.com/bazel-contrib/rules_python/issues/1777))
* (py_wheel) `bzlmod` installations now provide a `twine` setup for the default
Python toolchain in `rules_python` for version 3.11.
* (bzlmod) New `experimental_index_url`, `experimental_extra_index_urls` and
`experimental_index_url_overrides` to `pip.parse` for using the bazel
downloader. If you see any issues, report in
- [#1357](https://github.com/bazelbuild/rules_python/issues/1357). The URLs for
+ [#1357](https://github.com/bazel-contrib/rules_python/issues/1357). The URLs for
the whl and sdist files will be written to the lock file. Controlling whether
the downloading of metadata is done in parallel can be done using
`parallel_download` attribute.
@@ -1053,7 +1053,7 @@
`experimental_requirement_cycles`, now is a good time to migrate.
[python_default_visibility]: gazelle/README.md#directive-python_default_visibility
-[test_file_pattern_issue]: https://github.com/bazelbuild/rules_python/issues/1816
+[test_file_pattern_issue]: https://github.com/bazel-contrib/rules_python/issues/1816
[test_file_pattern_docs]: gazelle/README.md#directive-python_test_file_pattern
[20240224]: https://github.com/indygreg/python-build-standalone/releases/tag/20240224.
[20240415]: https://github.com/indygreg/python-build-standalone/releases/tag/20240415.
@@ -1061,7 +1061,7 @@
## [0.31.0] - 2024-02-12
-[0.31.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.31.0
+[0.31.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.31.0
### Changed
@@ -1073,7 +1073,7 @@
## [0.30.0] - 2024-02-12
-[0.30.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.30.0
+[0.30.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.30.0
### Changed
@@ -1105,7 +1105,7 @@
* (PyRuntimeInfo) Switch back to builtin PyRuntimeInfo for Bazel 6.4 and when
pystar is disabled. This fixes an error about `target ... does not have ...
PyRuntimeInfo`.
- ([#1732](https://github.com/bazelbuild/rules_python/issues/1732))
+ ([#1732](https://github.com/bazel-contrib/rules_python/issues/1732))
### Added
@@ -1147,7 +1147,7 @@
## [0.29.0] - 2024-01-22
-[0.29.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.29.0
+[0.29.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.29.0
### Changed
@@ -1167,7 +1167,7 @@
* (bzlmod pip.parse) Use a platform-independent reference to the interpreter
pip uses. This reduces (but doesn't eliminate) the amount of
platform-specific content in `MODULE.bazel.lock` files; Follow
- [#1643](https://github.com/bazelbuild/rules_python/issues/1643) for removing
+ [#1643](https://github.com/bazel-contrib/rules_python/issues/1643) for removing
platform-specific content in `MODULE.bazel.lock` files.
* (wheel) The stamp variables inside the distribution name are no longer
@@ -1199,7 +1199,7 @@
## [0.28.0] - 2024-01-07
-[0.28.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.28.0
+[0.28.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.28.0
### Changed
@@ -1225,7 +1225,7 @@
* (toolchains) `py_runtime` can now take an executable target. Note: runfiles
from the target are not supported yet.
- ([#1612](https://github.com/bazelbuild/rules_python/issues/1612))
+ ([#1612](https://github.com/bazel-contrib/rules_python/issues/1612))
* (gazelle) When `python_generation_mode` is set to `file`, create one `py_binary`
target for each file with `if __name__ == "__main__"` instead of just one
@@ -1252,7 +1252,7 @@
package (e.g. one for the package, one for an extra) now work.
* (bzlmod python.toolchain) Submodules can now (re)register the Python version
that rules_python has set as the default.
- ([#1638](https://github.com/bazelbuild/rules_python/issues/1638))
+ ([#1638](https://github.com/bazel-contrib/rules_python/issues/1638))
* (whl_library) Actually use the provided patches to patch the whl_library.
On Windows the patching may result in files with CRLF line endings, as a result
the RECORD file consistency requirement is lifted and now a warning is emitted
@@ -1261,13 +1261,13 @@
file if you decide to do so.
* (coverage): coverage reports are now created when the version-aware
rules are used.
- ([#1600](https://github.com/bazelbuild/rules_python/issues/1600))
+ ([#1600](https://github.com/bazel-contrib/rules_python/issues/1600))
* (toolchains) Workspace builds register the py cc toolchain (bzlmod already
was). This makes e.g. `//python/cc:current_py_cc_headers` Just Work.
- ([#1669](https://github.com/bazelbuild/rules_python/issues/1669))
+ ([#1669](https://github.com/bazel-contrib/rules_python/issues/1669))
* (bzlmod python.toolchain) The value of `ignore_root_user_error` is now decided
by the root module only.
- ([#1658](https://github.com/bazelbuild/rules_python/issues/1658))
+ ([#1658](https://github.com/bazel-contrib/rules_python/issues/1658))
### Added
@@ -1280,7 +1280,7 @@
## [0.27.0] - 2023-11-16
-[0.27.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.27.0
+[0.27.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.27.0
### Changed
@@ -1446,7 +1446,7 @@
* (gazelle) Improve runfiles lookup hermeticity.
-[0.26.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.26.0
+[0.26.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.26.0
## [0.25.0] - 2023-08-22
@@ -1474,7 +1474,7 @@
* (gazelle) Stop generating unnecessary imports.
* (toolchains) s390x supported for Python 3.9.17, 3.10.12, and 3.11.4.
-[0.25.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.25.0
+[0.25.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.25.0
## [0.24.0] - 2023-07-11
@@ -1510,4 +1510,4 @@
* (pip) Create all_data_requirements alias
* Expose Python C headers through the toolchain.
-[0.24.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.24.0
+[0.24.0]: https://github.com/bazel-contrib/rules_python/releases/tag/0.24.0
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index cd27486..17558e1 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -30,7 +30,7 @@
(More advanced users may prefer the GitHub UI and raw `git` commands).
```shell
-gh repo fork bazelbuild/rules_python --clone --remote
+gh repo fork bazel-contrib/rules_python --clone --remote
```
Next, make sure you have a new enough version of Python installed that supports the
diff --git a/RELEASING.md b/RELEASING.md
index 42a2921..6e441cb 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -32,7 +32,7 @@
To find if there were any features added or incompatible changes made, review
[CHANGELOG.md](CHANGELOG.md) and the commit history. This can be done using
github by going to the url:
-`https://github.com/bazelbuild/rules_python/compare/<VERSION>...main`.
+`https://github.com/bazel-contrib/rules_python/compare/<VERSION>...main`.
## Patch release with cherry picks
diff --git a/WORKSPACE b/WORKSPACE
index b97411e..3ad83ca 100644
--- a/WORKSPACE
+++ b/WORKSPACE
@@ -107,7 +107,7 @@
# which we need to fetch in order to compile it.
load("@rules_python_gazelle_plugin//:deps.bzl", _py_gazelle_deps = "gazelle_deps")
-# See: https://github.com/bazelbuild/rules_python/blob/main/gazelle/README.md
+# See: https://github.com/bazel-contrib/rules_python/blob/main/gazelle/README.md
# This rule loads and compiles various go dependencies that running gazelle
# for python requirements.
_py_gazelle_deps()
@@ -118,7 +118,7 @@
#####################
# Install twine for our own runfiles wheel publishing.
# Eventually we might want to install twine automatically for users too, see:
-# https://github.com/bazelbuild/rules_python/issues/1016.
+# https://github.com/bazel-contrib/rules_python/issues/1016.
load("@rules_python//python:pip.bzl", "pip_parse")
pip_parse(
diff --git a/docs/api/rules_python/python/config_settings/index.md b/docs/api/rules_python/python/config_settings/index.md
index cb44de9..79c7d0c 100644
--- a/docs/api/rules_python/python/config_settings/index.md
+++ b/docs/api/rules_python/python/config_settings/index.md
@@ -266,7 +266,7 @@
time.
This is only intended to work around
-[#2489](https://github.com/bazelbuild/rules_python/issues/2489), where some
+[#2489](https://github.com/bazel-contrib/rules_python/issues/2489), where some
packaging rules don't support `declare_symlink()` artifacts.
Values:
diff --git a/docs/conf.py b/docs/conf.py
index 4c8e4a2..f58baf5 100644
--- a/docs/conf.py
+++ b/docs/conf.py
@@ -104,7 +104,7 @@
# Insert after the main extension
extensions.insert(1, "readthedocs_ext.external_version_warning")
readthedocs_vcs_url = (
- "http://github.com/bazelbuild/rules_python/pull/{}".format(
+ "http://github.com/bazel-contrib/rules_python/pull/{}".format(
os.environ.get("READTHEDOCS_VERSION", "")
)
)
@@ -133,7 +133,7 @@
# --- Extlinks configuration
extlinks = {
- "gh-path": (f"https://github.com/bazelbuild/rules_python/tree/main/%s", "%s"),
+ "gh-path": (f"https://github.com/bazel-contrib/rules_python/tree/main/%s", "%s"),
}
# --- MyST configuration
diff --git a/docs/extending.md b/docs/extending.md
index dbd63e5..387310e 100644
--- a/docs/extending.md
+++ b/docs/extending.md
@@ -23,7 +23,7 @@
behavior of a core rule.
:::
-Follow or comment on https://github.com/bazelbuild/rules_python/issues/1647
+Follow or comment on https://github.com/bazel-contrib/rules_python/issues/1647
for the development of APIs to support custom derived rules.
## Creating custom rules
diff --git a/docs/getting-started.md b/docs/getting-started.md
index b3b5409..9697166 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -18,7 +18,7 @@
```starlark
# Update the version "0.0.0" to the release found here:
-# https://github.com/bazelbuild/rules_python/releases.
+# https://github.com/bazel-contrib/rules_python/releases.
bazel_dep(name = "rules_python", version = "0.0.0")
pip = use_extension("@rules_python//python/extensions:pip.bzl", "pip")
@@ -39,13 +39,13 @@
load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
# Update the snippet based on the latest release below
-# https://github.com/bazelbuild/rules_python/releases
+# https://github.com/bazel-contrib/rules_python/releases
http_archive(
name = "rules_python",
sha256 = "ca77768989a7f311186a29747e3e95c936a41dffac779aff6b443db22290d913",
strip_prefix = "rules_python-0.36.0",
- url = "https://github.com/bazelbuild/rules_python/releases/download/0.36.0/rules_python-0.36.0.tar.gz",
+ url = "https://github.com/bazel-contrib/rules_python/releases/download/0.36.0/rules_python-0.36.0.tar.gz",
)
load("@rules_python//python:repositories.bzl", "py_repositories")
diff --git a/docs/pypi-dependencies.md b/docs/pypi-dependencies.md
index 28e630c..039200d 100644
--- a/docs/pypi-dependencies.md
+++ b/docs/pypi-dependencies.md
@@ -71,7 +71,7 @@
while Bazel is fetching dependencies. For example, if you produce a reusable Bazel module
such as a ruleset, you may want to include the requirements.bzl file rather than make your users
install the WORKSPACE setup to generate it.
-See https://github.com/bazelbuild/rules_python/issues/608
+See https://github.com/bazel-contrib/rules_python/issues/608
This is the same workflow as Gazelle, which creates `go_repository` rules with
[`update-repos`](https://github.com/bazelbuild/bazel-gazelle#update-repos)
@@ -180,7 +180,7 @@
buildozer 'substitute deps @old//([^/]+) @new//${1}' //...:*
```
-[requirements-drawbacks]: https://github.com/bazelbuild/rules_python/issues/414
+[requirements-drawbacks]: https://github.com/bazel-contrib/rules_python/issues/414
### Entry points
diff --git a/docs/toolchains.md b/docs/toolchains.md
index 3294c17..0e4f5c2 100644
--- a/docs/toolchains.md
+++ b/docs/toolchains.md
@@ -273,7 +273,7 @@
To import rules_python in your project, you first need to add it to your
`WORKSPACE` file, using the snippet provided in the
-[release you choose](https://github.com/bazelbuild/rules_python/releases)
+[release you choose](https://github.com/bazel-contrib/rules_python/releases)
To depend on a particular unreleased version, you can do the following:
@@ -282,7 +282,7 @@
# Update the SHA and VERSION to the lastest version available here:
-# https://github.com/bazelbuild/rules_python/releases.
+# https://github.com/bazel-contrib/rules_python/releases.
SHA="84aec9e21cc56fbc7f1335035a71c850d1b9b5cc6ff497306f84cced9a769841"
@@ -292,7 +292,7 @@
name = "rules_python",
sha256 = SHA,
strip_prefix = "rules_python-{}".format(VERSION),
- url = "https://github.com/bazelbuild/rules_python/releases/download/{}/rules_python-{}.tar.gz".format(VERSION,VERSION),
+ url = "https://github.com/bazel-contrib/rules_python/releases/download/{}/rules_python-{}.tar.gz".format(VERSION,VERSION),
)
load("@rules_python//python:repositories.bzl", "py_repositories")
@@ -324,7 +324,7 @@
```
After registration, your Python targets will use the toolchain's interpreter during execution, but a system-installed interpreter
-is still used to 'bootstrap' Python targets (see https://github.com/bazelbuild/rules_python/issues/691).
+is still used to 'bootstrap' Python targets (see https://github.com/bazel-contrib/rules_python/issues/691).
You may also find some quirks while using this toolchain. Please refer to [python-build-standalone documentation's _Quirks_ section](https://gregoryszorc.com/docs/python-build-standalone/main/quirks.html).
## Autodetecting toolchain
diff --git a/examples/build_file_generation/WORKSPACE b/examples/build_file_generation/WORKSPACE
index 3f1fad8..6681ad6 100644
--- a/examples/build_file_generation/WORKSPACE
+++ b/examples/build_file_generation/WORKSPACE
@@ -59,7 +59,7 @@
# DON'T COPY_PASTE THIS.
# Our example uses `local_repository` to point to the HEAD version of rules_python.
# Users should instead use the installation instructions from the release they use.
-# See https://github.com/bazelbuild/rules_python/releases
+# See https://github.com/bazel-contrib/rules_python/releases
local_repository(
name = "rules_python",
path = "../..",
@@ -128,7 +128,7 @@
# which we need to fetch in order to compile it.
load("@rules_python_gazelle_plugin//:deps.bzl", _py_gazelle_deps = "gazelle_deps")
-# See: https://github.com/bazelbuild/rules_python/blob/main/gazelle/README.md
+# See: https://github.com/bazel-contrib/rules_python/blob/main/gazelle/README.md
# This rule loads and compiles various go dependencies that running gazelle
# for python requirements.
_py_gazelle_deps()
diff --git a/examples/bzlmod/py_proto_library/BUILD.bazel b/examples/bzlmod/py_proto_library/BUILD.bazel
index 175589f..969cb8e 100644
--- a/examples/bzlmod/py_proto_library/BUILD.bazel
+++ b/examples/bzlmod/py_proto_library/BUILD.bazel
@@ -18,7 +18,7 @@
],
)
-# Regression test for https://github.com/bazelbuild/rules_python/issues/2515
+# Regression test for https://github.com/bazel-contrib/rules_python/issues/2515
#
# This test fails before protobuf 30.0 release
# when ran with --legacy_external_runfiles=False (default in Bazel 8.0.0).
diff --git a/examples/bzlmod_build_file_generation/MODULE.bazel b/examples/bzlmod_build_file_generation/MODULE.bazel
index 30ad567..9bec25f 100644
--- a/examples/bzlmod_build_file_generation/MODULE.bazel
+++ b/examples/bzlmod_build_file_generation/MODULE.bazel
@@ -12,7 +12,7 @@
# The following stanza defines the dependency rules_python.
# For typical setups you set the version.
# See the releases page for available versions.
-# https://github.com/bazelbuild/rules_python/releases
+# https://github.com/bazel-contrib/rules_python/releases
bazel_dep(name = "rules_python", version = "0.0.0")
# The following loads rules_python from the file system.
@@ -25,7 +25,7 @@
# The following stanza defines the dependency rules_python_gazelle_plugin.
# For typical setups you set the version.
# See the releases page for available versions.
-# https://github.com/bazelbuild/rules_python/releases
+# https://github.com/bazel-contrib/rules_python/releases
bazel_dep(name = "rules_python_gazelle_plugin", version = "0.0.0")
# The following starlark loads the gazelle plugin from the file system.
diff --git a/examples/pip_parse_vendored/README.md b/examples/pip_parse_vendored/README.md
index fdf040c..baa51f5 100644
--- a/examples/pip_parse_vendored/README.md
+++ b/examples/pip_parse_vendored/README.md
@@ -1,7 +1,7 @@
# pip_parse vendored
This example is like pip_parse, however we avoid loading from the generated file.
-See https://github.com/bazelbuild/rules_python/issues/608
+See https://github.com/bazel-contrib/rules_python/issues/608
and https://blog.aspect.dev/avoid-eager-fetches.
The requirements now form a triple:
diff --git a/gazelle/BUILD.bazel b/gazelle/BUILD.bazel
index f74338d..0938be3 100644
--- a/gazelle/BUILD.bazel
+++ b/gazelle/BUILD.bazel
@@ -2,7 +2,7 @@
# Gazelle configuration options.
# See https://github.com/bazelbuild/bazel-gazelle#running-gazelle-with-bazel
-# gazelle:prefix github.com/bazelbuild/rules_python/gazelle
+# gazelle:prefix github.com/bazel-contrib/rules_python/gazelle
# gazelle:exclude bazel-out
gazelle(
name = "gazelle",
diff --git a/gazelle/README.md b/gazelle/README.md
index 01cf45a..89ebaef 100644
--- a/gazelle/README.md
+++ b/gazelle/README.md
@@ -17,7 +17,7 @@
## Example
-We have an example of using Gazelle with Python located [here](https://github.com/bazelbuild/rules_python/tree/main/examples/bzlmod).
+We have an example of using Gazelle with Python located [here](https://github.com/bazel-contrib/rules_python/tree/main/examples/bzlmod).
A fully-working example without using bzlmod is in [`examples/build_file_generation`](../examples/build_file_generation).
The following documentation covers using bzlmod.
@@ -29,7 +29,7 @@
See the installation `MODULE.bazel` snippet on the Releases page:
-https://github.com/bazelbuild/rules_python/releases in order to configure rules_python.
+https://github.com/bazel-contrib/rules_python/releases in order to configure rules_python.
You will also need to add the `bazel_dep` for configuration for `rules_python_gazelle_plugin`.
@@ -450,7 +450,7 @@
)
```
-[issue-1826]: https://github.com/bazelbuild/rules_python/issues/1826
+[issue-1826]: https://github.com/bazel-contrib/rules_python/issues/1826
#### Directive: `python_generation_mode_per_package_require_test_entry_point`:
When `# gazelle:python_generation_mode package`, whether a file called `__test__.py` or a target called `__test__`, a.k.a., entry point, is required to generate one test target per package. If this is set to true but no entry point is found, Gazelle will fall back to file mode and generate one test target per file. Setting this directive to false forces Gazelle to generate one test target per package even without entry point. However, this means the `main` attribute of the `py_test` will not be set and the target will not be runnable unless either:
@@ -553,7 +553,7 @@
```
Adding non-Python targets to the generated target is a feature request being
-tracked in [Issue #1865](https://github.com/bazelbuild/rules_python/issues/1865).
+tracked in [Issue #1865](https://github.com/bazel-contrib/rules_python/issues/1865).
The annotation can be added multiple times, and all values are combined
and de-duplicated.
diff --git a/gazelle/go.mod b/gazelle/go.mod
index 33ee6bb..91d27fd 100644
--- a/gazelle/go.mod
+++ b/gazelle/go.mod
@@ -1,4 +1,4 @@
-module github.com/bazelbuild/rules_python/gazelle
+module github.com/bazel-contrib/rules_python/gazelle
go 1.19
diff --git a/gazelle/manifest/BUILD.bazel b/gazelle/manifest/BUILD.bazel
index 33b5a46..ea81d85 100644
--- a/gazelle/manifest/BUILD.bazel
+++ b/gazelle/manifest/BUILD.bazel
@@ -8,7 +8,7 @@
go_library(
name = "manifest",
srcs = ["manifest.go"],
- importpath = "github.com/bazelbuild/rules_python/gazelle/manifest",
+ importpath = "github.com/bazel-contrib/rules_python/gazelle/manifest",
visibility = ["//visibility:public"],
deps = [
"@com_github_emirpasic_gods//sets/treeset",
diff --git a/gazelle/manifest/generate/BUILD.bazel b/gazelle/manifest/generate/BUILD.bazel
index 96248f4..77d2467 100644
--- a/gazelle/manifest/generate/BUILD.bazel
+++ b/gazelle/manifest/generate/BUILD.bazel
@@ -4,7 +4,7 @@
go_library(
name = "generate_lib",
srcs = ["generate.go"],
- importpath = "github.com/bazelbuild/rules_python/gazelle/manifest/generate",
+ importpath = "github.com/bazel-contrib/rules_python/gazelle/manifest/generate",
visibility = ["//visibility:public"],
deps = ["//manifest"],
)
diff --git a/gazelle/manifest/generate/generate.go b/gazelle/manifest/generate/generate.go
index 899b151..5210071 100644
--- a/gazelle/manifest/generate/generate.go
+++ b/gazelle/manifest/generate/generate.go
@@ -28,7 +28,7 @@
"os"
"strings"
- "github.com/bazelbuild/rules_python/gazelle/manifest"
+ "github.com/bazel-contrib/rules_python/gazelle/manifest"
)
func main() {
diff --git a/gazelle/manifest/hasher/BUILD.bazel b/gazelle/manifest/hasher/BUILD.bazel
index 2e7b125..c6e3c4c 100644
--- a/gazelle/manifest/hasher/BUILD.bazel
+++ b/gazelle/manifest/hasher/BUILD.bazel
@@ -3,7 +3,7 @@
go_library(
name = "hasher_lib",
srcs = ["main.go"],
- importpath = "github.com/bazelbuild/rules_python/gazelle/manifest/hasher",
+ importpath = "github.com/bazel-contrib/rules_python/gazelle/manifest/hasher",
visibility = ["//visibility:private"],
)
diff --git a/gazelle/manifest/manifest_test.go b/gazelle/manifest/manifest_test.go
index e80c7fc..320361a 100644
--- a/gazelle/manifest/manifest_test.go
+++ b/gazelle/manifest/manifest_test.go
@@ -22,7 +22,7 @@
"strings"
"testing"
- "github.com/bazelbuild/rules_python/gazelle/manifest"
+ "github.com/bazel-contrib/rules_python/gazelle/manifest"
)
var modulesMapping = manifest.ModulesMapping{
diff --git a/gazelle/manifest/test/test.go b/gazelle/manifest/test/test.go
index a7647f3..5804a71 100644
--- a/gazelle/manifest/test/test.go
+++ b/gazelle/manifest/test/test.go
@@ -27,7 +27,7 @@
"testing"
"github.com/bazelbuild/rules_go/go/runfiles"
- "github.com/bazelbuild/rules_python/gazelle/manifest"
+ "github.com/bazel-contrib/rules_python/gazelle/manifest"
)
func TestGazelleManifestIsUpdated(t *testing.T) {
diff --git a/gazelle/python/BUILD.bazel b/gazelle/python/BUILD.bazel
index 893c82e..eb2d72e 100644
--- a/gazelle/python/BUILD.bazel
+++ b/gazelle/python/BUILD.bazel
@@ -26,7 +26,7 @@
# See following for more info:
# https://github.com/bazelbuild/bazel-gazelle/issues/1513
embedsrcs = ["stdlib_list.txt"], # keep # TODO: use user-defined version?
- importpath = "github.com/bazelbuild/rules_python/gazelle/python",
+ importpath = "github.com/bazel-contrib/rules_python/gazelle/python",
visibility = ["//visibility:public"],
deps = [
"//manifest",
diff --git a/gazelle/python/configure.go b/gazelle/python/configure.go
index a369a64..7b1f091 100644
--- a/gazelle/python/configure.go
+++ b/gazelle/python/configure.go
@@ -27,8 +27,8 @@
"github.com/bazelbuild/bazel-gazelle/rule"
"github.com/bmatcuk/doublestar/v4"
- "github.com/bazelbuild/rules_python/gazelle/manifest"
- "github.com/bazelbuild/rules_python/gazelle/pythonconfig"
+ "github.com/bazel-contrib/rules_python/gazelle/manifest"
+ "github.com/bazel-contrib/rules_python/gazelle/pythonconfig"
)
// Configurer satisfies the config.Configurer interface. It's the
diff --git a/gazelle/python/generate.go b/gazelle/python/generate.go
index b1ac668..27930c1 100644
--- a/gazelle/python/generate.go
+++ b/gazelle/python/generate.go
@@ -32,7 +32,7 @@
"github.com/emirpasic/gods/sets/treeset"
godsutils "github.com/emirpasic/gods/utils"
- "github.com/bazelbuild/rules_python/gazelle/pythonconfig"
+ "github.com/bazel-contrib/rules_python/gazelle/pythonconfig"
)
const (
diff --git a/gazelle/python/resolve.go b/gazelle/python/resolve.go
index 88a688f..7a2ec3d 100644
--- a/gazelle/python/resolve.go
+++ b/gazelle/python/resolve.go
@@ -30,7 +30,7 @@
"github.com/emirpasic/gods/sets/treeset"
godsutils "github.com/emirpasic/gods/utils"
- "github.com/bazelbuild/rules_python/gazelle/pythonconfig"
+ "github.com/bazel-contrib/rules_python/gazelle/pythonconfig"
)
const languageName = "py"
diff --git a/gazelle/python/testdata/directive_python_default_visibility/README.md b/gazelle/python/testdata/directive_python_default_visibility/README.md
index be42792..60582d6 100644
--- a/gazelle/python/testdata/directive_python_default_visibility/README.md
+++ b/gazelle/python/testdata/directive_python_default_visibility/README.md
@@ -18,4 +18,4 @@
they interact with sub-packages.
-[gh-1682]: https://github.com/bazelbuild/rules_python/issues/1682
+[gh-1682]: https://github.com/bazel-contrib/rules_python/issues/1682
diff --git a/gazelle/python/testdata/directive_python_test_file_pattern_no_value/README.md b/gazelle/python/testdata/directive_python_test_file_pattern_no_value/README.md
index 2c38eb7..d6fb0b6 100644
--- a/gazelle/python/testdata/directive_python_test_file_pattern_no_value/README.md
+++ b/gazelle/python/testdata/directive_python_test_file_pattern_no_value/README.md
@@ -5,4 +5,4 @@
See discussion in [PR #1819 (comment)][comment].
-[comment]: https://github.com/bazelbuild/rules_python/pull/1819#discussion_r1536906287
+[comment]: https://github.com/bazel-contrib/rules_python/pull/1819#discussion_r1536906287
diff --git a/gazelle/python/testdata/with_third_party_requirements_from_imports/README.md b/gazelle/python/testdata/with_third_party_requirements_from_imports/README.md
index c50a1ca..8713d3d 100644
--- a/gazelle/python/testdata/with_third_party_requirements_from_imports/README.md
+++ b/gazelle/python/testdata/with_third_party_requirements_from_imports/README.md
@@ -12,4 +12,4 @@
from google.cloud import aiplatform, storage
```
-See https://github.com/bazelbuild/rules_python/issues/709 and https://github.com/sramirezmartin/gazelle-toy-example.
+See https://github.com/bazel-contrib/rules_python/issues/709 and https://github.com/sramirezmartin/gazelle-toy-example.
diff --git a/gazelle/pythonconfig/BUILD.bazel b/gazelle/pythonconfig/BUILD.bazel
index d80902e..711bf2e 100644
--- a/gazelle/pythonconfig/BUILD.bazel
+++ b/gazelle/pythonconfig/BUILD.bazel
@@ -6,7 +6,7 @@
"pythonconfig.go",
"types.go",
],
- importpath = "github.com/bazelbuild/rules_python/gazelle/pythonconfig",
+ importpath = "github.com/bazel-contrib/rules_python/gazelle/pythonconfig",
visibility = ["//visibility:public"],
deps = [
"//manifest",
diff --git a/gazelle/pythonconfig/pythonconfig.go b/gazelle/pythonconfig/pythonconfig.go
index fde0a98..2183ec6 100644
--- a/gazelle/pythonconfig/pythonconfig.go
+++ b/gazelle/pythonconfig/pythonconfig.go
@@ -23,7 +23,7 @@
"github.com/emirpasic/gods/lists/singlylinkedlist"
"github.com/bazelbuild/bazel-gazelle/label"
- "github.com/bazelbuild/rules_python/gazelle/manifest"
+ "github.com/bazel-contrib/rules_python/gazelle/manifest"
)
// Directives
diff --git a/python/packaging.bzl b/python/packaging.bzl
index 17f72a7..629af2d 100644
--- a/python/packaging.bzl
+++ b/python/packaging.bzl
@@ -139,7 +139,7 @@
To publish the wheel to PyPI, the twine package is required and it is installed
by default on `bzlmod` setups. On legacy `WORKSPACE`, `rules_python`
doesn't provide `twine` itself
- (see https://github.com/bazelbuild/rules_python/issues/1016), but
+ (see https://github.com/bazel-contrib/rules_python/issues/1016), but
you can install it with `pip_parse`, just like we do any other dependencies.
Once you've installed twine, you can pass its label to the `twine`
diff --git a/python/private/py_cc_toolchain_rule.bzl b/python/private/py_cc_toolchain_rule.bzl
index d5f3b68..f12933e 100644
--- a/python/private/py_cc_toolchain_rule.bzl
+++ b/python/private/py_cc_toolchain_rule.bzl
@@ -15,7 +15,7 @@
"""Implementation of py_cc_toolchain rule.
NOTE: This is a beta-quality feature. APIs subject to change until
-https://github.com/bazelbuild/rules_python/issues/824 is considered done.
+https://github.com/bazel-contrib/rules_python/issues/824 is considered done.
"""
load("@bazel_skylib//rules:common_settings.bzl", "BuildSettingInfo")
diff --git a/python/private/py_console_script_gen.py b/python/private/py_console_script_gen.py
index 64ebea6..ffc4e81 100644
--- a/python/private/py_console_script_gen.py
+++ b/python/private/py_console_script_gen.py
@@ -17,7 +17,7 @@
For Python versions earlier than 3.11 and for earlier bazel versions than 7.0 we need to workaround the issue of
sys.path[0] breaking out of the runfiles tree see the following for more context:
-* https://github.com/bazelbuild/rules_python/issues/382
+* https://github.com/bazel-contrib/rules_python/issues/382
* https://github.com/bazelbuild/bazel/pull/15701
In affected bazel and Python versions we see in programs such as `flake8`, `pylint` or `pytest` errors because the
@@ -130,7 +130,7 @@
module, _, entry_point = entry_point.rpartition(":")
attr, _, _ = entry_point.partition(".")
# TODO: handle 'extras' in entry_point generation
- # See https://github.com/bazelbuild/rules_python/issues/1383
+ # See https://github.com/bazel-contrib/rules_python/issues/1383
# See https://packaging.python.org/en/latest/specifications/entry-points/
with open(out, "w") as f:
diff --git a/python/private/py_runtime_rule.bzl b/python/private/py_runtime_rule.bzl
index 9407cac..3dc00ba 100644
--- a/python/private/py_runtime_rule.bzl
+++ b/python/private/py_runtime_rule.bzl
@@ -269,7 +269,7 @@
NOTE: the runfiles of the target may not yet be properly respected/propagated
to consumers of the toolchain/interpreter, see
- bazelbuild/rules_python/issues/1612
+ bazel-contrib/rules_python/issues/1612
For a platform runtime (i.e. `interpreter_path` being set) this attribute must
not be set.
diff --git a/python/private/pypi/patch_whl.bzl b/python/private/pypi/patch_whl.bzl
index c839f2e..7af9c4d 100644
--- a/python/private/pypi/patch_whl.bzl
+++ b/python/private/pypi/patch_whl.bzl
@@ -128,7 +128,7 @@
warning_msg = """WARNING: the resultant RECORD file of the patch wheel is different
If you are patching on Windows, you may see this warning because of
- a known issue (bazelbuild/rules_python#1639) with file endings.
+ a known issue (bazel-contrib/rules_python#1639) with file endings.
If you would like to silence the warning, you can apply the patch that is stored in
{record_patch}. The contents of the file are below:
diff --git a/python/private/pypi/pip_repository.bzl b/python/private/pypi/pip_repository.bzl
index 029566e..7976cfa 100644
--- a/python/private/pypi/pip_repository.bzl
+++ b/python/private/pypi/pip_repository.bzl
@@ -228,7 +228,7 @@
Optional annotations to apply to packages. Keys should be package names, with
capitalization matching the input requirements file, and values should be
generated using the `package_name` macro. For example usage, see [this WORKSPACE
-file](https://github.com/bazelbuild/rules_python/blob/main/examples/pip_repository_annotations/WORKSPACE).
+file](https://github.com/bazel-contrib/rules_python/blob/main/examples/pip_repository_annotations/WORKSPACE).
""",
),
_template = attr.label(
@@ -336,7 +336,7 @@
while Bazel is fetching dependencies. For example, if you produce a reusable Bazel module
such as a ruleset, you may want to include the requirements.bzl file rather than make your users
install the WORKSPACE setup to generate it.
-See https://github.com/bazelbuild/rules_python/issues/608
+See https://github.com/bazel-contrib/rules_python/issues/608
This is the same workflow as Gazelle, which creates `go_repository` rules with
[`update-repos`](https://github.com/bazelbuild/bazel-gazelle#update-repos)
diff --git a/python/private/pypi/whl_installer/namespace_pkgs.py b/python/private/pypi/whl_installer/namespace_pkgs.py
index 7d23c0e..b415844 100644
--- a/python/private/pypi/whl_installer/namespace_pkgs.py
+++ b/python/private/pypi/whl_installer/namespace_pkgs.py
@@ -92,7 +92,7 @@
ns_pkg_init_f.write(
textwrap.dedent(
"""\
- # __path__ manipulation added by bazelbuild/rules_python to support namespace pkgs.
+ # __path__ manipulation added by bazel-contrib/rules_python to support namespace pkgs.
__path__ = __import__('pkgutil').extend_path(__path__, __name__)
"""
)
diff --git a/python/private/pypi/whl_installer/wheel.py b/python/private/pypi/whl_installer/wheel.py
index 0f6bd27..d95b33a 100644
--- a/python/private/pypi/whl_installer/wheel.py
+++ b/python/private/pypi/whl_installer/wheel.py
@@ -378,6 +378,6 @@
source=wheel_source,
destination=destination,
additional_metadata={
- "INSTALLER": b"https://github.com/bazelbuild/rules_python",
+ "INSTALLER": b"https://github.com/bazel-contrib/rules_python",
},
)
diff --git a/python/private/python_repository.bzl b/python/private/python_repository.bzl
index 299dd36..0534f9c 100644
--- a/python/private/python_repository.bzl
+++ b/python/private/python_repository.bzl
@@ -154,9 +154,9 @@
)
uid = int(stdout.strip())
if uid == 0:
- fail_or_warn("The current user is root, which can cause spurious cache misses or build failures with the hermetic Python interpreter. See https://github.com/bazelbuild/rules_python/pull/713.")
+ fail_or_warn("The current user is root, which can cause spurious cache misses or build failures with the hermetic Python interpreter. See https://github.com/bazel-contrib/rules_python/pull/713.")
else:
- fail_or_warn("The current user has CAP_DAC_OVERRIDE set, which can cause spurious cache misses or build failures with the hermetic Python interpreter. See https://github.com/bazelbuild/rules_python/pull/713.")
+ fail_or_warn("The current user has CAP_DAC_OVERRIDE set, which can cause spurious cache misses or build failures with the hermetic Python interpreter. See https://github.com/bazel-contrib/rules_python/pull/713.")
python_bin = "python.exe" if ("windows" in platform) else "bin/python3"
@@ -188,7 +188,7 @@
# These pycache files are created on first use of the associated python files.
# Exclude them from the glob because otherwise between the first time and second time a python toolchain is used,"
# the definition of this filegroup will change, and depending rules will get invalidated."
- # See https://github.com/bazelbuild/rules_python/issues/1008 for unconditionally adding these to toolchains so we can stop ignoring them."
+ # See https://github.com/bazel-contrib/rules_python/issues/1008 for unconditionally adding these to toolchains so we can stop ignoring them."
"**/__pycache__/*.pyc",
"**/__pycache__/*.pyo",
]
diff --git a/python/private/runtime_env_toolchain_interpreter.sh b/python/private/runtime_env_toolchain_interpreter.sh
index 2cb7cc7..b09bc53 100755
--- a/python/private/runtime_env_toolchain_interpreter.sh
+++ b/python/private/runtime_env_toolchain_interpreter.sh
@@ -50,7 +50,7 @@
Please ensure an interpreter is available on this platform (and marked \
executable), or else register an appropriate Python toolchain as per the \
documentation for py_runtime_pair \
-(https://github.com/bazelbuild/rules_python/blob/master/docs/python.md#py_runtime_pair)."
+(https://github.com/bazel-contrib/rules_python/blob/master/docs/python.md#py_runtime_pair)."
fi
exec "$PYTHON_BIN" "$@"
diff --git a/python/private/stage1_bootstrap_template.sh b/python/private/stage1_bootstrap_template.sh
index bd142cf..e548c84 100644
--- a/python/private/stage1_bootstrap_template.sh
+++ b/python/private/stage1_bootstrap_template.sh
@@ -243,7 +243,7 @@
# using `kill`) to this process (the PID seen by the calling process) are
# received by the Python process. Otherwise, this process receives the signal
# and would have to manually propagate it.
-# See https://github.com/bazelbuild/rules_python/issues/2043#issuecomment-2215469971
+# See https://github.com/bazel-contrib/rules_python/issues/2043#issuecomment-2215469971
# for more information.
#
# However, we can't use exec when there is cleanup to do afterwards. Control
diff --git a/python/py_binary.bzl b/python/py_binary.bzl
index c7d57da..48ea768 100644
--- a/python/py_binary.bzl
+++ b/python/py_binary.bzl
@@ -38,9 +38,9 @@
**attrs: Rule attributes forwarded onto the underlying {rule}`py_binary`.
"""
if attrs.get("python_version") == "PY2":
- fail("Python 2 is no longer supported: https://github.com/bazelbuild/rules_python/issues/886")
+ fail("Python 2 is no longer supported: https://github.com/bazel-contrib/rules_python/issues/886")
if attrs.get("srcs_version") in ("PY2", "PY2ONLY"):
- fail("Python 2 is no longer supported: https://github.com/bazelbuild/rules_python/issues/886")
+ fail("Python 2 is no longer supported: https://github.com/bazel-contrib/rules_python/issues/886")
_py_binary_impl(**add_migration_tag(attrs))
diff --git a/python/py_library.bzl b/python/py_library.bzl
index 12354a7..8b8d468 100644
--- a/python/py_library.bzl
+++ b/python/py_library.bzl
@@ -37,7 +37,7 @@
**attrs: Rule attributes forwarded onto {rule}`py_library`.
"""
if attrs.get("srcs_version") in ("PY2", "PY2ONLY"):
- fail("Python 2 is no longer supported: https://github.com/bazelbuild/rules_python/issues/886")
+ fail("Python 2 is no longer supported: https://github.com/bazel-contrib/rules_python/issues/886")
_py_library_impl(**add_migration_tag(attrs))
diff --git a/python/py_runtime.bzl b/python/py_runtime.bzl
index 2c44523..dad2965 100644
--- a/python/py_runtime.bzl
+++ b/python/py_runtime.bzl
@@ -37,6 +37,6 @@
**attrs: Rule attributes forwarded onto {rule}`py_runtime`.
"""
if attrs.get("python_version") == "PY2":
- fail("Python 2 is no longer supported: see https://github.com/bazelbuild/rules_python/issues/886")
+ fail("Python 2 is no longer supported: see https://github.com/bazel-contrib/rules_python/issues/886")
_py_runtime_impl(**add_migration_tag(attrs))
diff --git a/python/py_runtime_pair.bzl b/python/py_runtime_pair.bzl
index b1e9041..26d378f 100644
--- a/python/py_runtime_pair.bzl
+++ b/python/py_runtime_pair.bzl
@@ -85,7 +85,7 @@
**attrs: Extra attrs passed onto the native rule
"""
if attrs.get("py2_runtime"):
- fail("PYthon 2 is no longer supported: see https://github.com/bazelbuild/rules_python/issues/886")
+ fail("PYthon 2 is no longer supported: see https://github.com/bazel-contrib/rules_python/issues/886")
_py_runtime_pair(
name = name,
py2_runtime = py2_runtime,
diff --git a/python/py_test.bzl b/python/py_test.bzl
index 7f6626e..b565773 100644
--- a/python/py_test.bzl
+++ b/python/py_test.bzl
@@ -38,9 +38,9 @@
**attrs: Rule attributes forwarded onto {rule}`py_test`.
"""
if attrs.get("python_version") == "PY2":
- fail("Python 2 is no longer supported: https://github.com/bazelbuild/rules_python/issues/886")
+ fail("Python 2 is no longer supported: https://github.com/bazel-contrib/rules_python/issues/886")
if attrs.get("srcs_version") in ("PY2", "PY2ONLY"):
- fail("Python 2 is no longer supported: https://github.com/bazelbuild/rules_python/issues/886")
+ fail("Python 2 is no longer supported: https://github.com/bazel-contrib/rules_python/issues/886")
# buildifier: disable=native-python
_py_test_impl(**add_migration_tag(attrs))
diff --git a/python/runfiles/BUILD.bazel b/python/runfiles/BUILD.bazel
index a541b29..2040403 100644
--- a/python/runfiles/BUILD.bazel
+++ b/python/runfiles/BUILD.bazel
@@ -39,7 +39,7 @@
# This can be manually tested by running tests/runfiles/runfiles_wheel_integration_test.sh
# We ought to have an automated integration test for it, too.
-# see https://github.com/bazelbuild/rules_python/issues/1002
+# see https://github.com/bazel-contrib/rules_python/issues/1002
py_wheel(
name = "wheel",
# From https://pypi.org/classifiers/
@@ -50,7 +50,7 @@
description_file = "README.md",
dist_folder = "dist",
distribution = "bazel_runfiles",
- homepage = "https://github.com/bazelbuild/rules_python",
+ homepage = "https://github.com/bazel-contrib/rules_python",
python_requires = ">=3.7",
strip_path_prefixes = ["python"],
twine = None if BZLMOD_ENABLED else "@rules_python_publish_deps_twine//:pkg",
diff --git a/sphinxdocs/docs/readthedocs.md b/sphinxdocs/docs/readthedocs.md
index 66e4be8..c347d19 100644
--- a/sphinxdocs/docs/readthedocs.md
+++ b/sphinxdocs/docs/readthedocs.md
@@ -119,7 +119,7 @@
# Insert after the main extension
extensions.insert(1, "readthedocs_ext.external_version_warning")
readthedocs_vcs_url = (
- "http://github.com/bazelbuild/rules_python/pull/{}".format(
+ "http://github.com/bazel-contrib/rules_python/pull/{}".format(
os.environ.get("READTHEDOCS_VERSION", "")
)
)
diff --git a/tests/integration/custom_commands_test.py b/tests/integration/custom_commands_test.py
index f78ee46..2e9cb74 100644
--- a/tests/integration/custom_commands_test.py
+++ b/tests/integration/custom_commands_test.py
@@ -19,7 +19,7 @@
class CustomCommandsTest(runner.TestCase):
- # Regression test for https://github.com/bazelbuild/rules_python/issues/1840
+ # Regression test for https://github.com/bazel-contrib/rules_python/issues/1840
def test_run_build_python_zip_false(self):
result = self.run_bazel("run", "--build_python_zip=false", "//:bin")
self.assert_result_matches(result, "bazel-out")
diff --git a/tests/no_unsafe_paths/test.py b/tests/no_unsafe_paths/test.py
index 1f6cd4e..893add2 100644
--- a/tests/no_unsafe_paths/test.py
+++ b/tests/no_unsafe_paths/test.py
@@ -32,7 +32,7 @@
# < Python 3.11 behaviour
if (major, minor) < (3, 11):
- # Because of https://github.com/bazelbuild/rules_python/blob/0.39.0/python/private/stage2_bootstrap_template.py#L415-L436
+ # Because of https://github.com/bazel-contrib/rules_python/blob/0.39.0/python/private/stage2_bootstrap_template.py#L415-L436
self.assertEqual(os.path.dirname(sys.argv[0]), sys.path[0])
self.assertEqual(os.path.basename(sys.path[1]), archive)
# >= Python 3.11 behaviour
diff --git a/tests/packaging/BUILD.bazel b/tests/packaging/BUILD.bazel
index cc04c05..bb12269 100644
--- a/tests/packaging/BUILD.bazel
+++ b/tests/packaging/BUILD.bazel
@@ -32,7 +32,7 @@
main = "bin.py",
target_compatible_with = SUPPORTS_BOOTSTRAP_SCRIPT,
# Needed until https://github.com/bazelbuild/rules_pkg/issues/929 is fixed
- # See: https://github.com/bazelbuild/rules_python/issues/2489
+ # See: https://github.com/bazel-contrib/rules_python/issues/2489
venvs_use_declare_symlink = "no",
)
diff --git a/third_party/rules_pycross/pycross/private/tools/wheel_installer.py b/third_party/rules_pycross/pycross/private/tools/wheel_installer.py
index c03c4c2..a122e67 100644
--- a/third_party/rules_pycross/pycross/private/tools/wheel_installer.py
+++ b/third_party/rules_pycross/pycross/private/tools/wheel_installer.py
@@ -90,7 +90,7 @@
destination=destination,
# Additional metadata that is generated by the installation tool.
additional_metadata={
- "INSTALLER": b"https://github.com/bazelbuild/rules_python/tree/main/third_party/rules_pycross",
+ "INSTALLER": b"https://github.com/bazel-contrib/rules_python/tree/main/third_party/rules_pycross",
},
)
finally:
