PEP 8 — Style Guide for Python Code.

van Rossum, G., Warsaw, B., & Coghlan, N. (2001). PEP 8 — Style Guide for Python Code.

Type

Book chapter

Intellectual base

Review or monograph

Year

2001

Link

https://peps.python.org/pep-0008/

Cited from

biology_ecology

Cited by

1 citation across 1 artifact.

Each citation links to the sentence it supports in the citing article.

Primes

• Naming Convention
  • In programming and software, case styles, package conventions, branch-naming rules, and endpoint conventions constrain the form of identifiers.

    This sourceThe reference naming-and-style convention for an entire programming community, prescribing casing schemes, package conventions, and identifier form.

    Supported in partVerified against the work's full text

    PEP 8 prescribes case styles (CapWords, lowercase, mixedCase) and package/module naming, but nothing on branch naming or endpoint conventions.

    “Modules should have short, all-lowercase names. Underscores can be used in the module name if it improves readability. Python packages should also have short, all-lowercase names”

    Read by an automated reader; not a human review. How support was checked

Verification

Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.

Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Registry ID ref:68263a90f019 · see in the full table