Python

For Observed

Newcomers to programming and experienced developers alike, plus the community that builds and funds Python (Get Started widget; PSF band).

Problem Published

Development speed and maintenance cost: compile steps, hard-to-read code and glue work between systems (paraphrase of the executive summary).

Promise Observed

Work quickly and integrate systems effectively, with a language that is easy to learn and to read.

PSF mission (quoted in part, the rest paraphrased) Published

To "promote, protect, and advance the Python programming language", and to help a diverse, international community of Python programmers grow.

Proof behind each pillar

• Quick and easy to learn. Beginner's Guide linked from the Get Started widget.
• Quick and easy to learn. The official Python Tutorial at docs.python.org.
• Readable, productive code. PEP 20, The Zen of Python: "Readability counts."
• Readable, productive code. Five runnable code samples on the homepage (functions, control flow, lists, arithmetic, input/output).
• Use it for everything. Six application areas with named libraries (Django, PyTorch, SciPy, Ansible...).
• Use it for everything. PyPI hosts thousands of third-party modules (About page).
• Free, open and community-run. OSI-approved open source licence, freely usable and distributable, even commercially.
• Free, open and community-run. Stewarded by the PSF, a US 501(c)(3) non-profit membership organization.

Story Published

The PSF is a non-profit that holds Python's intellectual property, produces the free core distribution and protects the Python name; its mission statement was approved in 2002 and amended through 2009. The two-snakes logo was drawn by Tim Parkin around 2005, when Python moved from a "cute" animal icon to a mark balancing formality and playfulness, and he assigned it to the PSF. python.org has carried a copyright line since 2001.

Values

Category. General-purpose, interpreted, high-level open source programming language Published

Why them

1. Readable syntax that lowers the cost of program maintenance. Published
2. A large standard library plus PyPI's third-party modules. Published
3. Free, OSI-approved licence that allows commercial use. Published
4. No compilation step: a fast edit-test-debug cycle. Published
5. A non-profit foundation and a global community of conferences and user groups. Published

Instead of

Other programming languages: experienced programmers "in any other language" are invited to switch (hero slide).

Boilerplate Published

Python is an interpreted, object-oriented, high-level programming language with dynamic semantics, a clean, readable syntax and a large standard library, available free for all major platforms. It is developed under an OSI-approved open source license administered by the Python Software Foundation.

Taglines

They never claim

• Never imply the PSF endorses a course, book, project or certification; it endorses none (FAQ). Published
• Never claim exclusivity ("The Python Academy", "Python Inc.") or official status. Published
• Never use the logo to refer to anything but the Python programming language. Published

The homepage carries no slogan. It states one sentence (Python lets you work quickly and integrate systems more effectively), then proves it with code, a version number, news and a list of uses. The PSF adds its mission and two asks: become a member, donate.

Source: python.org/%20(2026-10-31)python.org/aboutpython.org/doc/essays/blurbpython.org/psf/mission

• Title case headlines
• In documentation, sentence case section titles are preferred; consistency within a unit matters more
• Use simple language; avoid esoteric phrasing for a world-wide audience
• Say “for example”, not “e.g.”
• Say “that is”, not “i.e.”
• Spell out an acronym at first use, full term first with the acronym in parentheses; HTML and UTF-8 need no expansion
• Say “allowlist”, not “whitelist”
• Say “blocklist”, not “blacklist”
• Say “main, parent/child, server/client, primary/secondary”, not “master/slave”
• Say “free-threaded”, not “No-GIL”
• Hyphenate open-source as an adjective (open-source software); no hyphen as a noun (open source is a collaboration model)
• Python is always capitalized; Unicode capitalized; reST starts lowercase; POSIX uppercase
• Affirmative tone: state what the language does; no "dangerous" or "experts only" except real security risks
• Economy of expression: err on the side of succinct
• No author bylines on community documentation
• Use "Python" as an adjective followed by a generic noun; never as a verb
• First or most prominent mention of the Python word mark takes ®, except email, online discussion, non-graphical ads and academic papers
• Third parties add a notice: "Python" and the Python Logo are trademarks of the PSF, and a non-affiliation line

PlainWelcomingConfidentPrecise

Python publishes writing rules for its documentation (devguide style guide) and, through PEP 20, the values behind them. The homepage voice is short, friendly and factual, with Title Case labels.

• Simple English; spell out acronyms at first use
• "for example" and "that is", never e.g./i.e.
• allowlist/blocklist, main/primary, free-threaded
• Affirmative: say what works and how
• Be succinct; short concrete code examples
• No bylines on community docs
• "Python" as an adjective before a generic noun

• Two voices. The python.org homepage speaks in short, friendly, factual lines to newcomers and experienced developers alike; Title Case labels, a code sample as the hero, links named after where they go. The documentation voice (devguide style guide) is plainer still: simple words for a world-wide audience, affirmative statements, no hype.
• A landing page follows the homepage voice and anatomy. The docs rules (simple language, no Latin abbreviations, inclusive terms, affirmative tone) apply to all body copy.
• Respect the reader's intelligence: lay out the information and connect the dots without talking down (devguide, Audience).
• State what Python does and how to use it well; leave value judgements like "experts only" out (devguide, Affirmative tone).
• Trademark grammar: "Python" is an adjective before a generic noun (the Python programming language), never a verb (PSF trademark policy).
• Show, then tell: the homepage leads with runnable code and a one-line explanation, the way the docs prefer short concrete examples.

Source: peps.python.org/pep-0020devguide.python.org/documentation/style-guidepython.org/psf/mission

Source: devguide.python.org/documentation/style-guidepeps.python.org/pep-0020python.org/psf/trademarkspython.org/%20(2026-10-31)

The combined logo is the two-snakes device beside a "python" wordmark set in Flux Regular, with TM. The device may be used alone on the same terms. The PSF publishes the files (PNG, PSD, SVG), the Python Powered badges, and a three-page usage PDF of permitted and forbidden variants. Anyone may use the unaltered logo to refer to Python; derived logos need approval.

Source: python.org/community/logospython.org/psf/trademarkspython.org/psf/trademarks-faqs3.dualstack.us-east-2.amazonaws.com/pythondotorg-assets/media/files/Python-Logo-Usage-Guidelines-v1.0.pdf

No colour page is published. The colours come from the official logo files (blue and yellow snake gradients) and from python.org's open-source stylesheet, which names them: Python blue #3776AB, Python yellow #FFD343, blue-dark #1E415E, blue-medium #2B5B84, plus greys and a green, purple and red used only to code the network tabs.

Not published: colour proportions; print values (PMS, CMYK); contrast rules.

Source: github.com/python/pythondotorg/blob/main/static/css/style.cssgithub.com/python/pythondotorg/blob/b806afadb9ed2e3e8e923678c07d94f649249190/static/sass/_base.scsspython.org/static/community_logos/python-logo-generic.svgpython.org/%20(2026-10-31)

The logo names its face: Flux Regular, which the PSF cannot distribute. python.org uses Flux webfonts for short labels (widget titles, >>> marks, footer headings) and Source Sans Pro (open, OFL) for everything else, with Georgia italic for quotes and a system monospace stack for code.

Source: python.org/community/logospython.org/psf/trademarks-faqgithub.com/python/pythondotorg/blob/main/static/css/style.cssgithub.com/python/pythondotorg/blob/b806afadb9ed2e3e8e923678c07d94f649249190/static/sass/_base.scsspython.org/%20(2026-10-31)

The recognisable bits are interpreter marks and early-web gloss: ">>>" before every read-more link, a ">_" shell button, code panels, small gradient buttons with 6px corners and a white text-shadow, widgets topped by a 4px light-blue rule, and a yellow quote bubble with a tail.

Source: python.org/%20(2026-10-31)github.com/python/pythondotorg/blob/main/static/css/style.css

Source: github.com/python/pythondotorg/tree/main/static/fontspython.org/%20(2026-10-31)

Python publishes no illustration style and the homepage uses none. The only graphic beyond the logo and icons is code. The FAQ shows community logo designs (PyCon Zimbabwe, PyCon Israel, PyCon China) as approved derivatives, which is the nearest thing to an illustration guide.

Source: python.org/psf/trademarks-faq

No photography guidance is published and the homepage carries no photographs. Success stories are text quotes.

Source: python.org/%20(2026-10-31)

Source: github.com/python/pythondotorg/blob/main/static/css/style.csspython.org/static/js/main-min.b1e587ad1920.jspython.org/static/stylesheets/mq.ab4b4ea88926.css