Skip to content
GitHub no longer supports this web browser. Learn more about the browsers we support.
Commits on Oct 18, 2019
  1. Fix in Pet Peeves example for consistency (#1208)

    ShaynAli authored and encukou committed Oct 18, 2019
Commits on Sep 23, 2019
  1. PEP 8: Discourage use of return/break/continue in finally (#1174)

    dpgeorge authored and Guido van Rossum committed Sep 23, 2019
Commits on Mar 13, 2019
  1. PEP 8: minor grammar improvement (#926)

    Mariatta authored and gvanrossum committed Mar 13, 2019
    From 
    > does not import objects whose name starts with an underscore.
    into
    > does not import objects whose names start with an underscore.
    
    Closes python/pythondotorg#1387
Commits on Feb 23, 2019
  1. Update pep-0008.txt (#854)

    andresdelfino authored and warsaw committed Feb 23, 2019
Commits on Jan 9, 2019
  1. PEP 8: Comment clarification (#861)

    0101011 authored and brettcannon committed Jan 9, 2019
Commits on Oct 29, 2018
  1. PEP 0008: Clarify self-contradictory =-spacing rules (#820)

    ExplodingCabbage authored and warsaw committed Oct 29, 2018
    Previously, the PEP contained roughly the following three rules, in sequence:
    
    1. Never use spaces around `=` when used to indicate a parameter default
    2. Something unrelated
    3. DO use spaces around `=` when used to indicate a parameter default if there is also a parameter annotation present
    
    This commit attempts to clarify this part of the PEP by:
    * Combining the first and third rules listed above into a single rule that addresses both annotated and unannotated parameters
    * Rephrasing the first rule to indicate that it applies only to unannotated parameters, to eliminate the logical contradiction
Commits on Jul 7, 2018
  1. PEP 8: Fix inconsistent use of line breaks, case and indentation (#664)

    maggyero authored and gvanrossum committed Jul 7, 2018
Commits on May 24, 2018
  1. Use consistent "backwards" adverb and case for heads (#637)

    maggyero authored and brettcannon committed May 24, 2018
Commits on Jan 19, 2018
  1. Add coding style recommendations for variable annotations (#548)

    ilevkivskyi authored and gvanrossum committed Jan 19, 2018
Commits on Jan 17, 2018
  1. PEP 8 Explicitly State Variable Names convention? #535 (#545)

    Carl-Ty authored and warsaw committed Jan 17, 2018
Commits on Dec 19, 2017
  1. abbreviation -> acronym (#517)

    jamesray1 authored and brettcannon committed Dec 19, 2017
Commits on Nov 11, 2017
  1. Revert "Rename all .txt PEP files to .rst (GH-462)" (GH-464)

    Mariatta committed Nov 11, 2017
    This reverts commit bb0e518.
  2. Rename all .txt PEP files to .rst (GH-462)

    mozillazg authored and Mariatta committed Nov 11, 2017
    For #1
Commits on Nov 10, 2017
  1. PEP 8, deindent some of the text. (GH-458)

    Mariatta committed Nov 10, 2017
Commits on Nov 6, 2017
  1. Update pep-0008.txt (#438)

    toonarmycaptain authored and warsaw committed Nov 6, 2017
    * Update pep-0008.txt
    
    Clarified contradictions regarding comment formatting. NB Complete sentences should have a period.
    
    * Update pep-0008.txt
    
    Changed to remove reference to short comments without terminating period.
    
    * Update pep-0008.txt
    
    Further refined, corrected incorrect, fixed  singular/plural.
    
    * Update pep-0008.txt
    
    * Update pep-0008.txt
    
    Edit for consistency use 'multi-' in 'multi-line` 'multi-statement` 'multi-sentence` etc with dash rather than space or no splitter (eg 'multi line`, 'multiline`). If a different convention is preferred, do that.
    
    * Update pep-0008.txt 'latin' capitalization
    
    'Latin' is a proper noun, and thus should be capitalized.
    
    * Update pep-0008.txt 'boolean' capitalization
    
    Capitalization should be consisted. I propose 'boolean' should always be capitalized, as per https://english.stackexchange.com/questions/4481/should-the-word-boolean-be-capitalized
    
    At present it is inconsistently capitalised.
    Changed 'boolean' to 'Boolean'
    
    * Update pep-0008.txt - 'unicode' capitalization
    
    Update pep-0008.txt - as a proper noun, 'unicode' should be capitalized. Fixed 3 instances.
    
    * Revise Update pep-0008.txt
    
    Removed revisions to 'boolean', 'unicode'. 
    
    Unicode capitalization [issue](https://bugs.python.org/issue31873) under discussion.
    
    * Removed trailing newlines
    
    Removed trailing newlines
    
    * Standardised 'multiline', reworded 'Latin'
    
    Made the form 'multiline' uniform throughout the document. 
    
    Clarified references to Latin alphabet to direct to the specific character set desired.
    
    * Removed errant period
    
    * Moved  'alphabet'
    
    Moved  'alphabet' before encoding parenthesis line 336.
Commits on Oct 25, 2017
  1. Update pep-0008.txt (#433)

    toonarmycaptain authored and warsaw committed Oct 25, 2017
    Update pep-0008.txt
    
    Clarified contradictions regarding comment formatting. NB Complete sentences should have a period.
Commits on Jul 12, 2017
  1. fix minor typos (#294)

    JDongian authored and brettcannon committed Jul 12, 2017
Commits on Jun 6, 2017
  1. Cross-reference PEP 3131 from PEP 8 (#286)

    ncoghlan committed Jun 6, 2017
    PEP 3131 (Unicode identifiers) includes a policy section
    covering their use within the standard library.
    
    This adds an explicit cross-reference to that section from
    the prescriptive naming conventions section of PEP 8.
Commits on Feb 14, 2017
  1. Clarify my preferences around trailing commas (#211)

    gvanrossum committed Feb 14, 2017
Commits on Aug 3, 2016
  1. [WIP] Semantics of variance in type variables and notation conventions (

    ilevkivskyi authored and gvanrossum committed Aug 3, 2016
    #68)
    
    * Semantics of variance in type variables and notation conventions
    
    * Notation convention for type variables in PEP 8
Commits on Jul 11, 2016
  1. Fix various typos, spelling and grammar errors

    intgr committed Jul 11, 2016
    Errors detected using Topy (https://github.com/intgr/topy), all changes
    verified by hand.
Commits on Jun 20, 2016
  1. Clarify backward-compatible type annotations

    ambv committed Jun 20, 2016
    Previous wording used the term "function annotations" which is overly generic. This commit modifies the wording to make it clear we don't mean arbitrary function annotations.
Commits on Jun 8, 2016
  1. Clarify dunders.

    warsaw committed Jun 8, 2016
Commits on Jun 7, 2016
  1. Relax __all__ location.

    warsaw committed Jun 7, 2016
    Put all module level dunders together in the same location, and remove
    the redundant version bookkeeping information.
    
    Closes #27187.  Patch by Ian Lee.
Commits on Jun 3, 2016
Commits on May 3, 2016
  1. Backed out changeset: c4aef26d128b

    serhiy-storchaka committed May 3, 2016
    Unknown interpreted text role "kbd".
  2. Use the kbd role.

    serhiy-storchaka committed May 3, 2016
Commits on Apr 20, 2016
  1. PEP-8 Update on Knuth style breaking of a long formula. #issue26780

    orsenthil committed Apr 20, 2016
    Patch by Brandon Rhodes provides clarity and rationale for this suggestion.
    Also fixes the example to use "+", "-" operators which have same precedence
    level.
    
    Reviewed by Guido van Rossum.
Commits on Apr 15, 2016
  1. Fix typo, resea[r]ch

    Rosuav committed Apr 15, 2016
Commits on Apr 14, 2016
Commits on Mar 21, 2016
  1. Just refer to the spec in PEP 484 for straddling annotations instead …

    gvanrossum committed Mar 21, 2016
    …of repeating the info in PEP 8.
Commits on Feb 22, 2016
  1. Gramatical and other improvements given by thefourtheye.

    warsaw committed Feb 22, 2016
    Closes #26408
Commits on Jan 5, 2016
Older
You can’t perform that action at this time.