Skip to content

PYBV11: 'sys.implementation[2]' does not reflect the build variant #16498

Closed
@hmaerki

Description

@hmaerki

Port, board and/or hardware

PYBV11

MicroPython version

v1.24.1 and before

Reproduction

flash different build-variants on a PYBV11 and call sys.implementation[2]

Expected behaviour

It would be beneficial, if sys.implementation[2] would differ for each variant. This is required by octoprobe to verify if the correct variant is flashed.

Observed behaviour

PYBV11

build: PYBV11

>>> sys.implementation[2]
'PYBv1.1 with STM32F405RG'

build: PYBV11-DP_TREAD

>>> sys.implementation[2]
'PYBv1.1 with STM32F405RG'  <<Wrong: I am missing  '-DP_TREAD'

In contrast the RP2

build: RP2

>>> sys.implementation[2]
'RP2350'

build: RP2-RISCV

>>> sys.implementation[2]
'RP2350-RISCV'  <<Ok: '-RISCV' is there

Additional Information

No response

Code of Conduct

Yes, I agree

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