Skip to content

refactor(pypi): return a list from parse_requirements #2931

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.

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

Merged
merged 1 commit into from
May 28, 2025

Conversation

aignas
Copy link
Collaborator

@aignas aignas commented May 24, 2025

The modeling of the data structures returned by the parse_requirements
function was not optimal and this was because historically there was
more logic in the extension.bzl and more things were decided there.

With the recent refactors it is possible to have a harder to misuse data
structure from the parse_requirements. For each package we will
return a struct which will have a srcs field that will contain easy to
consume values.

With this in place we can do the fix that is outlined in the referenced
issue.

Work towards #2648

The modeling of the data structures returned by the `parse_requirements`
function was not optimal and this was because historically there was
more logic in the `extension.bzl` and more things were decided there.

With the recent refactors it is possible to have a harder to misuse data
structure from the `parse_requirements`. For each `package` we will
return a struct which will have a `srcs` field that will contain easy to
consume values.

With this in place we can do the fix that is outlined in the referenced
issue.

Work towards bazel-contrib#2648
@aignas aignas added this pull request to the merge queue May 28, 2025
Merged via the queue into bazel-contrib:main with commit 369ca91 May 28, 2025
3 checks passed
@aignas aignas deleted the refactor/parse-requirements-model branch May 28, 2025 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants