GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Check and report PEP 11 support tier in configure · Issue #93491 · python/cpython

Check and report PEP 11 support tier in configure #93491

New issue
Copy link
New issue
Copy link
Closed
#93492
Closed
Check and report PEP 11 support tier in configure#93491
#93492
Copy link
Assignees
brettcannon
Labels
3.11only security fixesonly security fixes3.12only security fixesonly security fixesbuildThe build process and cross-buildThe build process and cross-buildtype-featureA feature request or enhancementA feature request or enhancement

Description

@tiran
tiran
opened on Jun 4, 2022
Issue body actions

Feature or enhancement

PEP 11 now defines support tiers based on CPU arch, platform, libc, and compiler. I propose to check the support level in configure and report it to the user. It is trivial to check the platform with a case block. The compiler name can be detect by builtin macro names like __clang__.

A message at build time makes support tier more obvious to the user. It might even nudge some vendors to contribute fixes and build bots.

Example:

checking for PEP 11 support tier... x86_64-pc-linux-gnu/gcc has tier 1 (supported)
checking for PEP 11 support tier... wasm32-unknown-emscripten/clang is not supported
...
configure: creating Modules/Setup.local
configure: creating Makefile
configure:

If you want a release build with all stable optimizations active (PGO, etc),
please run ./configure --enable-optimizations

configure:

Platform "wasm32-unknown-emscripten" with compiler "clang" is not supported by
CPython core team, see https://peps.python.org/pep-0011/ for more information.

Activity

  1. tiran
    added
    type-featureA feature request or enhancementA feature request or enhancement
    buildThe build process and cross-buildThe build process and cross-build
    3.11only security fixesonly security fixes
    3.12only security fixesonly security fixes
    on Jun 4, 2022
  2. tiran
    assigned
    brettcannon
    on Jun 4, 2022
  3. erlend-aasland
    linked a pull request that will close this issuegh-93491: Add support tier detection to configure (GH-93492) #93492on Jun 10, 2022
  4. tiran
    closed this as completedin #93492on Jun 10, 2022
  5. miss-islington
    added a commit that references this issue on Jun 10, 2022

    pythongh-93491: Add support tier detection to configure (pythonGH-93492)

    a739db0
  6. tiran
    added a commit that references this issue on Jun 10, 2022

    gh-93491: Add support tier detection to configure (GH-93492)

    3124d9a
  7. miss-islington
    added a commit that references this issue on Jun 10, 2022

    gh-93491: Add support tier detection to configure (GH-93492)

    516d90e
  8. serhiy-storchaka
    added a commit that references this issue on Jun 26, 2022

    Revert 30935 defer bpo45162 to 312 (#94285)

    1ffde3e
  9. tiran
    added 2 commits that reference this issue on Jun 30, 2022

    pythongh-93491: Fix PEP 11 tier detection for FreeBSD

    f9e9505

    gh-93491: Fix PEP 11 tier detection for FreeBSD (GH-94441)

    67d208f
  10. miss-islington
    added 2 commits that reference this issue on Jun 30, 2022

    pythongh-93491: Fix PEP 11 tier detection for FreeBSD (pythonGH-94441)

    2698fee

    gh-93491: Fix PEP 11 tier detection for FreeBSD (GH-94441)

    8ee4e12
  11. gvanrossum
    added a commit that references this issue on Jun 30, 2022

    pythongh-93491: Fix PEP 11 tier detection for FreeBSD (pythonGH-94441)

    9eb94f3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @brettcannon
    brettcannon

Labels

3.11only security fixesonly security fixes3.12only security fixesonly security fixesbuildThe build process and cross-buildThe build process and cross-buildtype-featureA feature request or enhancementA feature request or enhancement

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402503 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.