Skip to content

PEP 342 is outdated #64529

Closed
Closed

Description

@msmhrt
mannequin
BPO 20330
Nosy @ncoghlan, @bitdancer

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2014-01-25.08:03:40.216>
created_at = <Date 2014-01-21.15:08:11.993>
labels = ['invalid', 'docs']
title = 'PEP 342 is outdated'
updated_at = <Date 2014-01-25.08:03:40.214>
user = 'https://bugs.python.org/msmhrt'

bugs.python.org fields:

activity = <Date 2014-01-25.08:03:40.214>
actor = 'ncoghlan'
assignee = 'docs@python'
closed = True
closed_date = <Date 2014-01-25.08:03:40.216>
closer = 'ncoghlan'
components = ['Documentation']
creation = <Date 2014-01-21.15:08:11.993>
creator = 'msmhrt'
dependencies = []
files = []
hgrepos = []
issue_num = 20330
keywords = []
message_count = 3.0
messages = ['208650', '208658', '209163']
nosy_count = 4.0
nosy_names = ['ncoghlan', 'r.david.murray', 'docs@python', 'msmhrt']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue20330'
versions = ['Python 3.3']

Activity

  1. msmhrt commented on Jan 21, 2014

    msmhrtmannequin
    MannequinAuthor

    Although PEP-342 says foo(yield 42) is legal, Lib/test/test_grammar.py says:

       # Requires parentheses as call argument
       def g(): f((yield 1))
       check_syntax_error(self, "def g(): f(yield 1)")
    

    BTW, It seems that foo(yield 42) written in ECMAScript 6 is OK.

  2. bitdancer commented on Jan 21, 2014

    @bitdancer
    Member

    Most PEPs are historical documents once they are final, so I don't think there is actually anything to fix here. But I could be wrong.

  3. ncoghlan commented on Jan 25, 2014

    @ncoghlan
    Contributor

    David is correct, most PEPs are historical records of design decisions that cease to be updated once completed. The language reference is the normative guide for current behaviour.

    The exception is "informational" and "process" PEPs, which cover things that are not covered in the language reference, as well the occasional Standards Track PEP which ends up not being incorporated into the language reference properly (for example, until the import section was added to the language reference in Python 3.3, PEP-302 was the best available reference documentation).

  4. transferred this issue fromon Apr 10, 2022
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

    docsDocumentation in the Doc dir

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions