-
-
Notifications
You must be signed in to change notification settings - Fork 42
[Bug]: Python 3.11 #159
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
Comments
I ran into the same problem when trying to switch from rules_python. |
Any ETA on this? Python 3.11 has been out for quite some time. And there is no evidence that these rules support it. Taking such a long time to support a Python release reduces confidence that these rules are being maintained. |
Use the original (source) interpreters bin path as the 'home' value in the generated `pyvenv.cfg` file. Closes #159 --- ### Type of change - Bug fix (change which fixes an issue) **For changes visible to end-users** - Suggested release notes are provided below: Ensure correct `home` pathing is used when generating the venv. ### Test plan - Covered by existing test cases - Manual testing; please provide instructions so we can reproduce: Updated e2e smoke to use py3.11
I'm still experiencing this bug using load("@aspect_rules_py//py:defs.bzl", "py_venv")
py_venv(
name = "venv",
) Then a simple:
The error goes away when downgrading the interpreter constraint to |
What happened?
When using a standalone Python 3.11 toolchain, the environment setup in the entrypoint template is not right.
If we set up the Python interpreter to be version 3.11 as in the reproduction section below, we get an error from the Python interpreter at launch.
Version
Development (host) and target OS/architectures:
Output of
bazel --version
:bazel 5.4.0
(but same error with latest version of Bazel)Version of the Aspect rules, or other relevant rules from your
WORKSPACE
orMODULE.bazel
file: HEAD of this repo -- commit913676de2f89b8272cdd14bc53f719534e58c31f
Language(s) and/or frameworks involved: Python
How to reproduce
Any other information?
This issue may be relevant here -- https://discuss.python.org/t/python3-11-seems-to-break-venv-created-from-non-system-python-with-zipped-stdlib/20874.
The text was updated successfully, but these errors were encountered: