You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current implementation of py3_image always imports py_binary from @rules_python//python:def.bzl. This results in py_binary using the default version used in python_multi_register_toolchains and there aren't ways to specify other python version.
This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days.
Collaborators can add an assignee to keep this open indefinitely. Thanks for your contributions to rules_docker!
🚀 feature request
Relevant Rules
py3_image
Description
We have multiple versions of python toolchains installed with
python_multi_register_toolchains
Current implementation of
py3_image
always importspy_binary
from@rules_python//python:def.bzl
. This results inpy_binary
using the default version used inpython_multi_register_toolchains
and there aren't ways to specify other python version.rules_docker/python3/image.bzl
Lines 96 to 102 in 6db7c12
Describe the solution you'd like
Not sure what the solution could look like 🤔
Describe alternatives you've considered
I'm using a temporarily patch to use other version's toolchain for now:
The text was updated successfully, but these errors were encountered: