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 — Implement PEP 695 · Issue #103763 · python/cpython

Implement PEP 695 #103763

New issue
Copy link
New issue
Copy link
Closed
Closed
Implement PEP 695#103763
Copy link
Assignees
JelleZijlstra
Labels
topic-typingtype-featureA feature request or enhancementA feature request or enhancement

Description

@JelleZijlstra
JelleZijlstra
opened on Apr 24, 2023
Issue body actions

We should implement PEP-695. Some discussion of the implementation is at https://github.com/erictraut/cpython/issues. I will open a draft PR momentarily.

TODO:

  • Evaluate TypeAlias values
  • Lazy evaluation for TypeVar bounds
  • More tests
  • Fix remaining tests in test_typing.py

Linked PRs

  • gh-103763: Implement PEP 695 #103764
Reacted by Kirill Podoprigora, Carl Meyer, sunmy2019 and Enderchief
Reacted by Kirill Podoprigora, Alex Prengère and Enderchief

Activity

  1. JelleZijlstra
    added
    type-featureA feature request or enhancementA feature request or enhancement
    on Apr 24, 2023
  2. JelleZijlstra
    self-assigned this
    on Apr 24, 2023
  3. preveen-stack commented on Apr 24, 2023

    @preveen-stack
    preveen-stack
    on Apr 24, 2023
    More actions

    PEP 695 – Type Parameter Syntax

  4. AlexWaygood
    added
    topic-typing
    on Apr 24, 2023
  5. sunmy2019 commented on Apr 24, 2023

    @sunmy2019
    sunmy2019
    on Apr 24, 2023
    Member
    More actions

    Wow. This syntax looks so cool. It reminds me of many generic expressions in other languages, such as C++ and Rust. (while the increases the learning curve of Python)

    I'll see what I can help here.

  6. preveen-stack commented on Apr 25, 2023

    @preveen-stack
    preveen-stack
    on Apr 25, 2023
    More actions

    I feel we should defend the intuitive readability of python irrespective of what.

  7. JelleZijlstra
    added a commit that references this issue on May 16, 2023

    gh-103763: Implement PEP 695 (#103764)

    24d8b88
  8. JelleZijlstra commented on May 16, 2023

    @JelleZijlstra
    JelleZijlstra
    on May 16, 2023
    MemberAuthor
    More actions

    The implementation is done. The next step is #103921, the documentation.

    Reacted by Maxim Martynov
  9. JelleZijlstra
    closed this as completedon May 16, 2023
  10. carljm
    added a commit that references this issue on May 16, 2023

    Merge branch 'main' into supermon

    a6dd626
  11. charliermarsh commented on Jun 22, 2023

    @charliermarsh
    charliermarsh
    on Jun 22, 2023
    More actions

    @JelleZijlstra - I'm sorry if this is the wrong place to ask, but is the specification and implementation of PEP 695 sufficiently stabilized that I could look into updating Ruff's parser and semantic model to support them?

  12. JelleZijlstra commented on Jun 22, 2023

    @JelleZijlstra
    JelleZijlstra
    on Jun 22, 2023
    MemberAuthor
    More actions

    I don't expect more major changes, no. There are currently no open PEP 695-related bugs; if anything else changes it would be as a result of new feedback we receive during the beta phase.

    Reacted by Charlie Marsh
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @JelleZijlstra
    JelleZijlstra

Labels

topic-typingtype-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.