Skip to content

[Issue]: Install defaults to python 3.14 with no override #956

Closed

Description

@astrelsky

Problem Description

The install either manually or through the dashboard automatically sets up an environment with python3.14. It should be 3.12.

Operating System

Ubuntu 26.04

CPU

AMD Ryzen™ AI Max+ 395

GPU

AMD Radeon™ 8060S

ROCm Version

N/A

Installation Method

Other (describe in Additional Information)

Installed ROCm Packages / Versions

None, was using rocm-cli to setup but it keeps insisting on creating a python3.14 virtual environment instead of the correct python 3.12.

ROCm Component

No response

Steps to Reproduce

No response

(Optional for Linux users) Output of rocminfo --support

rocminfo --support output
Paste output here

Additional Information

Installed via curl -fsSL https://raw.githubusercontent.com/ROCm/rocm-cli/main/install.sh | sh as specified in the readme (why wasn't this an option to choose from?)

Activity

  1. added
    installationIssues related to installation of drivers or ROCm libraries
    questionFurther information is requested
    on Nov 9, 2026
  2. juhovainio commented on Nov 9, 2026

    @juhovainio
    Collaborator

    Thanks for the report! I looked into why you ended up on 3.14.

    The Python version that gets chosen depends on which ROCm SDK version the install resolves to: 7.14 uses 3.12, ROCm 10 and newer use 3.14. An unpinned install on the release channel currently gives 7.14.1 on 3.12 as default, so I think you got ROCm 10 either via --version 10.x.y or the nightly channel, which currently resolves to 10.1 (the dashboard's install step also has a Release/Nightly toggle). Could you share the output of rocm install sdk? It prints which Python it picked and why, and it would tell us which case this was.

    On the 3.14 itself: only the vLLM stack for ROCm 10 (vLLM, flash-attn, amd-aiter) is published for 3.14 only. The SDK and PyTorch wheels are published for 3.10-3.14, so forcing 3.14 for every ROCm 10 install is for sure stricter than it needs to be.

    #989 adds rocm install sdk --python-version 3.12 (3.10-3.14 for ROCm 10+). The default stays 3.14 since that's what vLLM needs, and with another version the automatic vLLM install is skipped with a note. It also documents the Python choice in the README.

    As for the CLI install script, install.sh only installs the rocm binary and doesn't touch the Python env, so there was nothing to choose there. The Python gets picked when you run rocm install sdk. Whether an unpinned release install should move to ROCm 10 is tracked in #813 :)

  3. astrelsky commented on Nov 9, 2026

    @astrelsky
    Author

    I did explicitly specify 10.1, due to significant improvements over 7.2. It is definitely unexpected to automatically derive the python version that way without a way to manually set it. I had assumed it was because the system python was 3.14.

    Unfortunately some things are still using 3.12, so having the option to specify what python version you want would be appreciated.

    I see #989, thank you. I couldn't see it while typing on the GitHub mobile app.

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

    installationIssues related to installation of drivers or ROCm librariesquestionFurther information is requested

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions