Skip to content

refactor(pypi): use a builder pattern for parsing requirements #3159

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

aignas
Copy link
Collaborator

@aignas aignas commented Aug 11, 2025

Whilst trying to finish the configuration API I bumped into the issue
that the API of the parse_requirements function does not lend itself
to building the configuration easily.

With this we will be able to build the configuration more easily and
have more customization without passing ever more complex structures
between the functions. What is more, I believe that it may be possible
to have more complex composable builders in the future to build the
whl_library args with a single build command instead of what we have
now.

Work towards #2747

Whilst trying to finish the configuration API I bumped into the issue
that the API of the `parse_requirements` function does not lend itself
to building the configuration easily.

With this we will be able to build the configuration more easily and
have more customization without passing ever more complex structures
between the functions. What is more, I believe that it may be possible
to have more complex composable builders in the future to build the
`whl_library` args with a single `build` command instead of what we have
now.

Work towards bazel-contrib#2747
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.

1 participant