Skip to content

Write pip extension metadata to the MODULE.bazel.lock file #2731

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
aignas opened this issue Apr 3, 2025 · 0 comments
Open

Write pip extension metadata to the MODULE.bazel.lock file #2731

aignas opened this issue Apr 3, 2025 · 0 comments
Labels
need: upstream support An issue that needs changes in upstream code P4 type: pip pip/pypi integration

Comments

@aignas
Copy link
Collaborator

aignas commented Apr 3, 2025

This has been split from #2434.

The idea of this is to leverage the feature from bazelbuild/bazel#24777 when it is available in order to make the SimpleAPI querying more efficient.
@aignas aignas added P4 need: upstream support An issue that needs changes in upstream code type: pip pip/pypi integration labels Apr 3, 2025
@aignas aignas mentioned this issue Apr 4, 2025
Merged
github-merge-queue bot pushed a commit that referenced this issue Apr 5, 2025
@aignas
fix(pypi): mark the extension reproducible (#2730)
2bc3577 
This will remove the merge conflicts and improve the usability when the
`MODULE.bazel.lock` is used together with `rules_python`. This means
that the lock file will not be used to read the `URL` and `sha256`
values for the Python sources when the `experimental_index_url` is used,
but the idea is that that information will be kept in repo cache.

Fixes #2434

Created #2731 to leverage the bazel feature to write immutable facts to
the lock file once it becomes available.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
need: upstream support An issue that needs changes in upstream code P4 type: pip pip/pypi integration
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aignas