Closed
Description
Currently, it's not easy to guess how Python was built just by looking at python -VV
output or sys.version
.
I propose to enhance sys.version
to include more details about how Python was configured for the build:
- debug or release build
- "shared" or "framework" build
- assertions enabled or not
- address/memory/undefined behavior sanitizer
- etc.
It should help me to more quickly identify if a buildbot was built in debug mode or release mode.
It should help to see how Python was optimized: with or without LTO and PGO optimizations?
It should help to quickly have an idea of which ABI is used: the "pystats" ABI is different than the "debug" than the "release" ABI.
Linked PRs
Metadata
Metadata
Assignees
Labels
An unexpected behavior, bug, or errorAn unexpected behavior, bug, or error