Skip to content

Announce rules_go v0.24.5, v0.23.13 [skip ci]#2690

Merged
jayconrod merged 1 commit intobazel-contrib:masterfrom
jayconrod:announce-releases
Oct 26, 2020
Merged

Announce rules_go v0.24.5, v0.23.13 [skip ci]#2690
jayconrod merged 1 commit intobazel-contrib:masterfrom
jayconrod:announce-releases

Conversation

@jayconrod
Copy link
Copy Markdown
Collaborator

No description provided.

@google-cla google-cla Bot added the cla: yes label Oct 26, 2020
@jayconrod jayconrod merged commit 8a2ba42 into bazel-contrib:master Oct 26, 2020
@jayconrod jayconrod deleted the announce-releases branch October 26, 2020 20:30
yushan26 pushed a commit to yushan26/rules_go that referenced this pull request Jun 16, 2025
…ontrib#2692)

This implements the PEP508 compliant marker evaluation in starlark and
removes the need for the Python interpreter when evaluating requirements
files passed to `pip.parse`. This makes the evaluation faster and allows
us to fix a few known issues (bazel-contrib#2690).

In the future the intent is to move the `METADATA` parsing to pure
starlark so that the `RequiresDist` could be parsed in starlark at the
macro evaluation or analysis phases. This should make it possible to
more easily solve the design problem that more and more things need to
be passed to `whl_library` as args to have a robust dependency parsing:
* bazel-contrib#2319 needs the full Python version to have correct cross-platform
compatible `METADATA` parsing and passing it to `Python` and back makes
  it difficult/annoying to implement.
* Parsing the `METADATA` file requires the precise list of target
  platform or the list of available packages in the `requirements.txt`.
  This means that without it we cannot trim the dependency tree in the
  `whl_library`. Doing this at macro loading phase allows us to depend
  on `.bzl` files in the `hub_repository` and more effectively pass
  information.

I can remotely see that this could become useful in `py_wheel` or an
building
wheels from sdists as the environment markers may be present in various
source
metadata as well. What is more `uv.lock` file has the env markers as
part of
the lock file information, so this might be useful there.

Work towards bazel-contrib#2423
Work towards bazel-contrib#260
Split from bazel-contrib#2629
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant