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
When users install torch_xla, they would get torchax as well.
Motivation
The xb.call_jax1 feature under heavy development uses torchax and we expect torchax usage to grow. In order for all users of torch_xla to use this feature, we need to include torchax in torch_xla wheels/dockers/etc.
Pitch
I think there are two approaches:
Make torchax its own Python wheel/package, and have torch_xla depend on it always.
Literally link all torchax files inside the torch_xla wheel/package. This approach might need to deal with some packaging subtleties because some users may have already installed torchax standalone and not sure what will happen when they also install torch_xla with its own torchax.
Either way, this probably requires some setup.py changes.
🚀 Feature
When users install
torch_xla
, they would gettorchax
as well.Motivation
The
xb.call_jax
1 feature under heavy development usestorchax
and we expecttorchax
usage to grow. In order for all users of torch_xla to use this feature, we need to includetorchax
intorch_xla
wheels/dockers/etc.Pitch
I think there are two approaches:
Make
torchax
its own Python wheel/package, and havetorch_xla
depend on it always.Literally link all
torchax
files inside thetorch_xla
wheel/package. This approach might need to deal with some packaging subtleties because some users may have already installedtorchax
standalone and not sure what will happen when they also installtorch_xla
with its owntorchax
.Either way, this probably requires some setup.py changes.
cc @qihqi
The text was updated successfully, but these errors were encountered: