-
Notifications
You must be signed in to change notification settings - Fork 26
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
Support for python 3.13.0? #125
Comments
heya. I just stumbled upon this (or something similar) yesterday. someone on slack helped me debug, and we found a solution/workaround. add in python.override(register_all_versions = True) I haven't yet fully understood the cause tho. these are my findings:
so it might be that pycross should use |
i just noticed something else. i got the following in my python.toolchain(
is_default = True,
python_version = "3.12",
) this normally would have caused the latest patch-level to be used (e.g. I don't know if that is due to the workaround or something else. |
@aignas just reported in slack that he found a bug on rules_python's end, which might be the root-cause for this. |
Thanks @betaboon ... looking forward for the next release of rules_python! |
Should this work with python 3.13.0?
When I try to use the new rules_python 0.37.1 and to use Python version 3.13.0, rules_pycross fails with this message:
The text was updated successfully, but these errors were encountered: