Skip to content

torchao release compatibility table #2919

Description

@vkuzo

This issue describes the compatibility matrix between torchao releases and its dependencies. If you are seeing an error when importing torchao that looks like this,

(pytorch_nightly) [vasiliy@devgpu007.eag6 ~/local]$ python -c "import torchao"
Fatal Python error: Aborted

then most likely you can resolve this error by ensuring that the torch version in your environment is compatible with the torch version used to build your torchao version.

torch

torchao version torch version torch version, torchao's Python API only
0.18.0dev (nightly) 2.12.0dev (nightly) 2.11.0, 2.10.0, 2.9.0
0.17.0 2.11.0+ 2.11.0, 2.10.0, 2.9.0
0.16.0 2.10.0 2.10.0, 2.9.0, 2.8.0
0.15.0 2.9.1 2.9.1, 2.8.0, 2.7.1
0.14.1 2.9.0 2.9.0, 2.8.0, 2.7.1
0.13.0 2.8.0 2.8.0, 2.7.1, 2.6.0
0.12.0 2.7.1, 2.6.0, 2.5.0 n/a

fbgemm_gpu

torchao has an optional runtime dependency on fbgemm_gpu. Please see https://docs.pytorch.org/FBGEMM/general/Releases.html for the compatibility matrix for fbgemm_gpu. Note that while torchao's Python API supports multiple torch versions, each fbgemm_gpu version only supports a single torch version. Therefore, if you are using torchao together with fbgemm_gpu, you should use the torch version corresponding to your fbgemm_gpu version.

Activity

  1. jerryzh168 commented on Sep 10, 2025

    @jerryzh168
    Contributor

    any ideas when we can fix the compatibility of torchao nightly with torch? currently it's blocking tests in vllm: https://github.com/vllm-project/vllm/pull/21982/files#diff-2fe466060a88bb6a57175df8ca7175849db82a2cf2ba082295d481ab57e58868R512

  2. yushangdi commented on Sep 11, 2025

    @yushangdi
    Contributor

    I'm also having the same issue here. Blocking testing executorch with torch nightly.

    I have torch on latest master (with some python-only local changes) '2.9.0a0+git3564a8a', and torchao torchao-0.14.0.dev20250909+cu126.

  3. yushangdi commented on Sep 11, 2025

    @yushangdi
    Contributor

    I'm also having the same issue here. Blocking testing executorch with torch nightly.

    I have torch on latest master (with some python-only local changes) '2.9.0a0+git3564a8a', and torchao torchao-0.14.0.dev20250909+cu126.

    I have it resolved by installing pip install fbgemm-gpu-nightly to override fbgemm-gpu. So far importing torchao doesn't error anymore. Not sure if there're any other issues if I actually run anything.

  4. jerryzh168 commented on Sep 11, 2025

    @jerryzh168
    Contributor

    executorch doesn't need fbgem-gpu I think? if you use torchao nightly, can you also use torch nightly in ET?

  5. vkuzo commented on Sep 15, 2025

    @vkuzo
    ContributorAuthor

    we also need to update the following check https://github.com/pytorch/ao/blob/ea8c00fc90c99f0bf19fe87d22eb186c3dd19bf6/torchao/__init__.py#L38C45-L38C76 for PyTorch 2.10.x, as str(torch.__version__) >= "2.9" will not work properly for PyTorch 2.10

  6. vkuzo commented on Sep 19, 2025

    @vkuzo
    ContributorAuthor

    @liangel-02 , https://github.com/facebookresearch/FBGEMM/pull/1900/files might be relevant here - this is fbgemm fixing the same issue in their repo

  7. steveepreston commented on Oct 15, 2025

    @steveepreston

    Getting the error on all versions:
    Skipping import of cpp extensions due to incompatible torch version 2.9.0+cu128 for torchao version 0.14.0
    Skipping import of cpp extensions due to incompatible torch version 2.8.0+cu129 for torchao version 0.14.0
    Skipping import of cpp extensions due to incompatible torch version 2.8.0+cu128 for torchao version 0.14.0

  8. NeonSludge commented on Oct 15, 2025

    @NeonSludge

    This makes it very hard to use torchao with latest versions of Ray Serve/vLLM:
    Skipping import of cpp extensions due to incompatible torch version 2.8.0+cu128 for torchao version 0.14.0

  9. vkuzo commented on Oct 15, 2025

    @vkuzo
    ContributorAuthor

    Hi folks, thank you for reporting, we are looking into this and will provide an update soon. Note that unless you actually need c++ or CUDA kernels that ship with torchao, you can ignore the warning and use the Python-only APIs without issues.

  10. atalman commented on Oct 15, 2025

    @atalman
    Contributor
  11. DefTruth commented on Oct 16, 2025

    @DefTruth

    still have this warning message for torch 2.9.0:

    Skipping import of cpp extensions due to incompatible torch version 2.9.0+cu128 for torchao version 0.14.0         Please see GitHub issue #2919 for more info
  12. steveepreston commented on Oct 16, 2025

    @steveepreston

    These frustrating warnings keeps appearing repeatedly on all envs I working. Please fix it or mute it

  13. andrewor14 commented on Oct 16, 2025

    @andrewor14
    Contributor

    Hi all, we plan to release a 0.14.1 as soon as possible. The new version will be built against 2.9.0 and it will load the cpp extensions when used against this version. You won't see this warning anymore.

  14. lisi31415926 commented on Oct 17, 2025

    @lisi31415926

    Are there any plans to support CUDA 13.0? Thank you.

  15. 44 remaining items

  16. Qubitium commented on Apr 16, 2026

    @Qubitium

    Can NOGIL get some love please?

    #3243
    Image

  17. yiakwy-xpu-ml-framework-team commented on May 6, 2026

    @yiakwy-xpu-ml-framework-team

    @vkuzo please update:

        # torchao == 0.16.0
        torchao_pytorch_compatible_versions = [ 
            # Built against torch 2.8.0
            (_parse_version("0.13.0"), _parse_version("2.8.0")),
            (_parse_version("0.14.0"), _parse_version("2.8.0")),
            # Built against torch 2.9.0
            (_parse_version("0.14.1"), _parse_version("2.9.0")),
            (_parse_version("0.14.1"), _parse_version("2.10.0.dev")),
            # Built against torch 2.9.1
            (_parse_version("0.15.0"), _parse_version("2.9.1")),
            (_parse_version("0.15.0"), _parse_version("2.10.0.dev")),
            # Built against torch 2.10.0
            (_parse_version("0.16.0"), _parse_version("2.10.0")),
            (_parse_version("0.16.0"), _parse_version("2.11.0.dev")),
            # current torchao version - to be deleted after version bump
            (_parse_version("0.16.0.dev"), _parse_version("2.9.1")),
            (_parse_version("0.16.0.dev"), _parse_version("2.10.0.dev")),
            (_parse_version("0.16.0.dev"), _parse_version("2.11.0.dev")),
            # next torchao version
            (_parse_version("0.17.0.dev"), _parse_version("2.10.0")),
            (_parse_version("0.17.0.dev"), _parse_version("2.11.0.dev")),
        ]
    

    The latest version to support torch 2.8.0cu is "0.13.0" (training platform in Hopper with stable support of cu12.8).

  18. andrewor14 commented on May 12, 2026

    @andrewor14
    Contributor

    Closing this issue since torchao 0.17.0 is now ABI stable against torch 2.11. We have removed the compatibility table for all future torchao versions starting with 0.17.0. Please refer to https://github.com/pytorch/ao/releases/tag/v0.17.0 for more details.

  19. FurkanGozukara commented on May 20, 2026

    @FurkanGozukara

    @andrewor14 for Torch 2.12.0 we can use 0.17.0? what should we use? there is stable torch 2.12.0

  20. todochenxi commented on Jun 12, 2026

    @todochenxi

    This issue describes the compatibility matrix between torchao releases and its dependencies. If you are seeing an error when importing torchao that looks like this,

    (pytorch_nightly) [vasiliy@devgpu007.eag6 ~/local]$ python -c "import torchao"
    Fatal Python error: Aborted
    then most likely you can resolve this error by ensuring that the torch version in your environment is compatible with the torch version used to build your torchao version.

    torch

    torchao version torch version torch version, torchao's Python API only
    0.18.0dev (nightly) 2.12.0dev (nightly) 2.11.0, 2.10.0, 2.9.0
    0.17.0 2.11.0+ 2.11.0, 2.10.0, 2.9.0
    0.16.0 2.10.0 2.10.0, 2.9.0, 2.8.0
    0.15.0 2.9.1 2.9.1, 2.8.0, 2.7.1
    0.14.1 2.9.0 2.9.0, 2.8.0, 2.7.1
    0.13.0 2.8.0 2.8.0, 2.7.1, 2.6.0
    0.12.0 2.7.1, 2.6.0, 2.5.0 n/a

    fbgemm_gpu

    torchao has an optional runtime dependency on fbgemm_gpu. Please see https://docs.pytorch.org/FBGEMM/general/Releases.html for the compatibility matrix for fbgemm_gpu. Note that while torchao's Python API supports multiple torch versions, each fbgemm_gpu version only supports a single torch version. Therefore, if you are using torchao together with fbgemm_gpu, you should use the torch version corresponding to your fbgemm_gpu version.

    you are best

  21. FurkanGozukara commented on Jul 10, 2026

    @FurkanGozukara

    you really should start releasing cuda 13 windows wheels

    with CODEX I was able to compile abi3 torch 2.13 cuda for windows for my followers

    Image
  22. unpinned this issue on Aug 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions