Merge branch 'main' into fix/lockfile-inconsistency

Author: aignas

.bazelci/presubmit.yml

@@ -94,6 +94,8 @@ buildifier:
   bazel: "7.x"
   environment:
     RULES_PYTHON_ENABLE_PYSTAR: "1"
+  build_flags:
+    - "--config=bazel7.x"
   test_flags:
     # The doc check tests fail because the Starlark implementation makes the
     # PyInfo and PyRuntimeInfo symbols become documented.

.bazelrc

@@ -33,4 +33,6 @@ build:rtd --stamp
 # Some bzl files contain repos only available under bzlmod
 build:rtd --enable_bzlmod
 
+common:bazel7.x --incompatible_python_disallow_native_rules
+
 build --lockfile_mode=update

CHANGELOG.md

@@ -23,6 +23,27 @@ A brief description of the categories of changes:
 {#v0-0-0}
 ## Unreleased
 
+### Changed
+- (bzlmod) `pip.parse` spoke repository naming has changed in places where the
+  users specify different package versions per platform in the same hub repository.
+  We advise the users to use the `hub` repository directly to avoid such breakage in
+  the future.
+
+### Added
+- (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
+  users setting {bzl:obj}`pip.parse.experimental_index_url`, but now users have
+  more options whilst we continue to work on stabilizing the experimental feature.
+
+### Fixed
+- (bzlmod) The extension evaluation has been adjusted to always generate the
+  same lock file irrespective if `experimental_index_url` is set by any module
+  or not. Fixes
+  [#2268](https://github.com/bazelbuild/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`
+
 [0.0.0]: https://github.com/bazelbuild/rules_python/releases/tag/0.0.0
 
 {#v0-0-0-changed}
@@ -31,11 +52,9 @@ A brief description of the categories of changes:
 
 {#v0-0-0-fixed}
 ### Fixed
-- The extension evaluation has been adjusted to always generate the same lock
-  file irrespective if `experimental_index_url` is set by any module or not.
-  Fixes [#2268](https://github.com/bazelbuild/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` until we have `sdist` cross-building from source fully working.
+* (rules) Setting `--incompatible_python_disallow_native_rules` no longer
+  causes rules_python rules to fail.
+  ([#2326](https://github.com/bazelbuild/rules_python/issues/2326).
 
 {#v0-0-0-added}
 ### Added

docs/precompiling.md

@@ -83,7 +83,7 @@ Note that any execution requirements values can be specified in the flag.
 * Mixing rules_python PyInfo with Bazel builtin PyInfo will result in pyc files
   being dropped.
 * Precompiled files may not be used in certain cases prior to Python 3.11. This
-  occurs due Python adding the directory of the binary's main `.py` file, which
+  occurs due to Python adding the directory of the binary's main `.py` file, which
   causes the module to be found in the workspace source directory instead of
   within the binary's runfiles directory (where the pyc files are). This can
   usually be worked around by removing `sys.path[0]` (or otherwise ensuring the

examples/build_file_generation/.bazelrc

@@ -6,3 +6,5 @@ build --enable_runfiles
 # The bzlmod version of this example is in examples/bzlmod_build_file_generation
 # Once WORKSPACE support is dropped, this example can be entirely deleted.
 build --experimental_enable_bzlmod=false
+
+common:bazel7.x --incompatible_python_disallow_native_rules

examples/bzlmod/.bazelrc

@@ -7,3 +7,4 @@ test --test_output=errors --enable_runfiles
 
 # Windows requires these for multi-python support:
 build --enable_runfiles
+common:bazel7.x --incompatible_python_disallow_native_rules

examples/bzlmod/MODULE.bazel.lock

@@ -6,3 +6,4 @@ build --enable_runfiles
 common --experimental_enable_bzlmod
 
 coverage --java_runtime_version=remotejdk_11
+common:bazel7.x --incompatible_python_disallow_native_rules

examples/bzlmod_build_file_generation/.bazelrc

@@ -4,3 +4,4 @@ test --test_output=errors
 build --enable_runfiles
 
 coverage --java_runtime_version=remotejdk_11
+common:bazel7.x --incompatible_python_disallow_native_rules

examples/multi_python_versions/.bazelrc

@@ -1,2 +1,3 @@
 # https://docs.bazel.build/versions/main/best-practices.html#using-the-bazelrc-file
 try-import %workspace%/user.bazelrc
+common:bazel7.x --incompatible_python_disallow_native_rules