Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

PEP 695: Lazy evaluation, concrete scoping semantics, other changes #3122

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 21 commits into from
May 8, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update pep-0695.rst
  • Loading branch information
JelleZijlstra authored May 4, 2023
commit 90101e15d9a8ea9319ff2b532bba3397da9ac675
2 changes: 1 addition & 1 deletion 2 pep-0695.rst
Original file line number Diff line number Diff line change
Expand Up @@ -899,7 +899,7 @@ clarify that the new scopes are for the most part like function scopes.
``def695`` scope that is immediately within a class scope, then names defined
in that class scope can be accessed within the ``def695`` scope. (Regular functions,
by contrast, cannot access names defined within an enclosing class scope.)
- The following constructs are disallowed anywhere within a ``def695`` scope, though
- The following constructs are disallowed directly within a ``def695`` scope, though
they may be used within other scopes nested inside a ``def695`` scope:

- ``yield``
Expand Down
Morty Proxy This is a proxified and sanitized view of the page, visit original site.