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

feat: default py_runtime version info to --python_version #2198

Conversation

rickeylev
Copy link
Contributor

This changes py_runtime to get its interpreter version from the --python_version flag if
it wasn't explicitly specified. This is useful in two contexts:

For the runtime env toolchains, a local toolchain, or platform interpreter (basically any
py_runtime without a known version), it allows getting some Python version into the
analysis phase, which allows e.g. precompiling.

For environments using embedded Python, it allows defining fewer (e.g. 1) py_runtime
target instead of one for every Python version. This is because py_runtime serves a minor
role in such builds.

@rickeylev rickeylev force-pushed the feat.default.runtime.version.to.pyver.flag branch from 2313a77 to 484d38b Compare September 6, 2024 21:19
…o feat.default.runtime.version.to.pyver.flag
@rickeylev rickeylev added this pull request to the merge queue Sep 8, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Sep 8, 2024
@rickeylev rickeylev added this pull request to the merge queue Sep 9, 2024
Merged via the queue into bazelbuild:main with commit fcd1d5e Sep 9, 2024
4 checks passed
@rickeylev rickeylev deleted the feat.default.runtime.version.to.pyver.flag branch September 9, 2024 22:53
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