Skip to content
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

wip: set the python_version_flag in the pythons_hub on bzlmod #2205

Closed

Conversation

aignas
Copy link
Collaborator

@aignas aignas commented Sep 9, 2024

This is a quick draft to discuss the structure where:

  • --python_version is defined within @rules_python when bzlmod is disabled.
  • --python_version is defined within @pythons_hub when bzlmod is enabled.

The later allows us to ensure that we can have the right value enforcement when
the user can add extra toolchains at will.

BREAKING: For backwards compatibility we still have the alias for the config
flag present in //python/config_settings:python_version, but we don't have
any is_python_3.x any more in there and they are moved to the @python_hubs
repository, users have to use those symbols instead.

@aignas aignas closed this Sep 11, 2024
@aignas aignas deleted the refactor/python-version-in-hub branch September 11, 2024 01:25
github-merge-queue bot pushed a commit that referenced this pull request Sep 17, 2024
This is a different take on #2205.

Summary:
- Remove version constraints from the
`//python/config_settings:python_version`.
- Remove `is_python_config_setting` macro and use a different
implementation to
  retain the same functionality.

This in general will improve the situation on how the toolchains are
registered
and hopefully is a step towards resolving issues for #2081.
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