Skip to content

PEP 695 -- Type Parameter Syntax: Proposed changes #186

Closed

Description

@JelleZijlstra

While implementing PEP-695 I ran into a few issues that I think are best addressed by changing the PEP. The biggest change is to make type alias values and TypeVar bounds and constraints lazily evaluated, in line with the proposed semantics of PEP-649.

The proposed changes are here: https://github.com/python/peps/pull/3122/files.

My implementation in python/cpython#103763 already implements the proposed semantics.

Please take a look and let me know if you agree with these changes.

Activity

  1. JelleZijlstra commented on May 4, 2023

    @JelleZijlstra
    MemberAuthor

    I pushed another proposed change: python/peps@f446963. This comes out of the discussion in https://discuss.python.org/t/please-consider-delaying-or-even-rejecting-pep-695/26408 and specifies the scoping rules more concretely. I believe it is consistent with the scoping rules already present in the PEP, but more concrete and precise.

  2. Yhg1s commented on May 8, 2023

    @Yhg1s
    Member

    The SC is happy with both of the proposed semantics changes, and the updated text.

  3. JelleZijlstra commented on May 8, 2023

    @JelleZijlstra
    MemberAuthor

    Thanks!

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    PEPPython Enhancement Proposal

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions