Skip to content

toolchain resolution may be wrong when python_version does not include a patch version #2685

Closed
@aignas

Description

@aignas

Whilst writing code for #2657 I noticed that the toolchain matching is acting weirdly when using X.Y format in the python_version field. I noticed that when I write 3.12, the first toolchain gets matched instead of the entry in MINOR_MAPPING.

The fix would be to change the ordering in the toolchain repo to first list the versions in the MINOR_MAPPING before listing the rest of the toolchains.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions