Skip to content

[Bug]: [email protected] regressed the usage of rules_python resulting in a breaking change for later releases #3823

Open
@qtica

Description

@qtica

What happened?

The latest [email protected] introduced in #3783 changed the behavior of utilizing rules_python's extensions. The pip.parse was changed from hub_name to name.

A later release of rules_python removed the name attribute from pip.parse. This regression of the attribute in the MODULE.bazel makes it impossible to upgrade to later rules_python versions with the new [email protected] version without patching.

Version

Development (host) and target OS/architectures: linux/linux

Output of bazel --version: 7.4.1

Version of relevant rules from the WORKSPACE or MODULE.bazel file: [email protected]

Language(s) and/or frameworks involved:

[email protected]

How to reproduce

In a MODULE.bazel file:

bazel_dep(name = "protoc-gen-validate", version = "1.2.1")
bazel_dep(name = "rules_python", version = "1.2.0-rc0")

Then run:

bazel mod deps --lockfile_mode=update

You will get an error about an unknown attribute name in pip.parse.

Any other information?

Additionally the version of rules_python was downgraded in this release's MODULE.abzel file, as well as the configuration for rules_python's extensions. These changes do not matter so much to me, but I do find it odd to move versions backwards in a newer release. But the main issue is just the regression of hub_name to name.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions