Tags: rickeylev/rules_python
Tags
build(deps): bump docutils from 0.22 to 0.22.2 in /tools/publish (baz… …el-contrib#3289) [//]: # (dependabot-start)⚠️ **Dependabot is rebasing this PR**⚠️ Rebasing might not happen immediately, so don't worry if this takes some time. Note: if you make any changes to this PR yourself, they will take precedence over the rebase. --- [//]: # (dependabot-end) [//]: # (dependabot-start)⚠️ **Dependabot is rebasing this PR**⚠️ Rebasing might not happen immediately, so don't worry if this takes some time. Note: if you make any changes to this PR yourself, they will take precedence over the rebase. --- [//]: # (dependabot-end) Bumps [docutils](https://github.com/rtfd/recommonmark) from 0.22 to 0.22.2. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/rtfd/recommonmark/commits">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
fix(core): do not assume rules_python runtime (bazel-contrib#3134) This change reverts the behaviour where we assume that particular attributes will be always present - if bazel is doing autoloading for WORKSPACE builds (7.6.1), then we will crash with attribute error. I could not think how to add a unit test, which would test this fix because it seems to only happen with a released version of rules_python where we are not using `local_repository` override. Fixes bazel-contrib#3119 --------- Co-authored-by: Richard Levasseur <richardlev@gmail.com> (cherry picked from commit acf7507) Cherry-pick notes: adjusted changelog to mention 1.5.2
fix(pypi): only generate namespace package shims if implicit namespac… …es are disabled (bazel-contrib#3059) The refactoring to move the pkgutil shim generation to build phase inverted the logic for when it should be activated. When `enable_implicit_namespace_pkgs=True`, it means to not generate the pkgutil shims ("respect the Python definition of the namespace package"). To fix, just invert the logic that activates it. A test will be added in a subsequent PR because the necessary helper isn't in the 1.5 branch. Fixes bazel-contrib#3038 --------- Co-authored-by: Ignas Anikevicius <240938+aignas@users.noreply.github.com> (cherry picked from commit 47c681b)
fix: work around version parsing by only parsing if site-packages is … …enabled (bazel-contrib#3031) There's a bug in the version string parser that doesn't handle local identifiers correctly. Thankfully, it's only activated in the experimental code path when site packages for libraries is eanbled. Moving the logic within that block works around it. Work around for bazel-contrib#3030 (cherry picked from commit aab2650)
fix: work around version parsing by only parsing if site-packages is … …enabled (bazel-contrib#3031) There's a bug in the version string parser that doesn't handle local identifiers correctly. Thankfully, it's only activated in the experimental code path when site packages for libraries is eanbled. Moving the logic within that block works around it. Work around for bazel-contrib#3030 (cherry picked from commit aab2650)
fix(pypi): namespace_pkgs should pass correct arguments (bazel-contri… …b#3026) It seems that the only function that did not have unit tests have bugs and the integration tests did not catch it because we weren't creating namespacepkg `__init__.py` files. This change fixes the bug, adds a unit test for the remaining untested function. Fixes bazel-contrib#3023 Co-authored-by: Richard Levasseur <richardlev@gmail.com> (cherry picked from commit 4978027)
fix(toolchains): use posix-compatible exec -a alternative (bazel-cont… …rib#3010) The `exec -a` command doesn't work in dash, the default shell for Ubuntu/debian. To work around, use `sh -c`, which is posix and dash compatible. This allows changing the argv0 while invoking a different command. Also adds a test to verify the the runtime_env toolchain works with bootstrap script. Fixes bazel-contrib#3009 (cherry picked from commit c4543cd)
fix: use platform_info.target_settings in toolchain aliases (bazel-co… …ntrib#3001) During the refactor we forgot one more place where the `flag_values` on the platform information was used. They were no longer populated and broke. The solution is to use `selects.config_setting_group` to maintain behaviour and in order to smoke test I have added a target to verify that the aliases work. Related to bazel-contrib#2875 Fixes bazel-contrib#2993 Co-authored-by: Richard Levasseur <richardlev@gmail.com> (cherry picked from commit 107a878)
fix: support pre-release versions and add new toolchain versions (baz… …el-contrib#2969) Add latest toolchain builds and attempt adding a beta build. This shows/tests that we can handle pre-release versions just fine and we are able to test the toolchain matching. Whilst at it it implements the static advertising of the remaining interpreter information. Fixes bazel-contrib#2837 --------- Co-authored-by: Richard Levasseur <richardlev@gmail.com>
fix(pypi): fix a typo in parse_simpleapi_html (bazel-contrib#2866) It seems that the integration tests that I thought were covering this had the same time. Added an assertion to the unit tests as well Fixes bazel-contrib#2863. (cherry picked from commit 9dfa3ab)
PreviousNext