Tags: geaden/rules_python
Tags
fix(bzlmod+gazelle): update BCR release presubmit to use correct exam… …ple (bazel-contrib#1264) The bzlmod-compatible build_file_generation example was moved to the bzlmod_build_file_generation example. This should fix the automatic build/release of the gazelle BCR module.
feat(bzlmod): Register a default toolchain (bazel-contrib#1259) This makes rules_python always provide a default toolchain when using bzlmod. Note that, unlike workspace builds, the default is not the local system Python (`@bazel_tools//tools/python:autodetecting_toolchain`). Instead, the default is a hermetic runtime, but no guarantees are made about the particular version used. In practice, it will be the latest available Python version. Work towards bazel-contrib#1233
feat(bzlmod): support entry_point macro (bazel-contrib#1220) Add `entry_point` macro to the repo generated by the `pip.parse` extension. This works by using the canonical label literal, so should work without users needing to add the spoke repos to the `use_repo` statement. We test this by having an extra folder in the `bzlmod` example. Fixes bazel-contrib#958.
feat: Support specifying multiple download URLs in tool_versions. (ba… …zel-contrib#1145) The interface of `repository_ctx.download` and `repository_ctx.download_and_extract` supports string lists as well as strings as the value of the `url` argument. This is the ultimate destination of the `url` attribute in the `tool_versions` dictionary, so it makes sense for it to support lists as well. It is often useful to provide multiple download URLs, e.g. when vendoring deps through a mirror (to guard against issues like [git archive checksums changing](https://github.blog/changelog/2023-01-30-git-archive-checksums-may-change/) while still keeping the canonical download URL) or in an airgapped setting (to support internal URLs alongside external URLs). This is also pretty common around Bazel repository rules that download things, e.g. [http_archive](https://bazel.build/rules/lib/repo/http#http_archive-urls), so it can be expected to work with `tool_versions` too.
test(core): Add analysis tests for base Python rules. (bazel-contrib#… …1102) This is to provide some regression tests for the Starlark rewrite. These tests are approximately the same as Bazel's Java-implemented tests. Work towards bazel-contrib#1069
chore: revert publish wheel on releases (bazel-contrib#1022) our 0.17 release is stuck on this step. Partially reverts bazel-contrib#995
fix(release): use correct GH workflows syntax (bazel-contrib#1020) See https://docs.github.com/en/actions/learn-github-actions/contexts#github-context
feat: produce publishable distribution archives (bazel-contrib#1019) * feat: produce publishable distribution archives Fixes bazel-contrib#741 * fix: give unique names to dist/ folders by default
PreviousNext