PEP 333
E552012
PEP 333 is the Python Enhancement Proposal that originally defined the Web Server Gateway Interface (WSGI), a standard for communication between Python web applications and web servers.
All labels observed (2)
How this entity was disambiguated
This entity first appeared as the object of triple T5838736 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PEP 333 Context triple: [WSGI, specifiedIn, PEP 333]
-
A.
PEP 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced in Python 3.10.
-
B.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
C.
PEP 636
PEP 636 is a Python Enhancement Proposal that serves as a tutorial-style guide to the structural pattern matching feature introduced in Python 3.10.
-
D.
PEP 635
PEP 635 is a Python Enhancement Proposal that provides a detailed rationale and motivation for the structural pattern matching feature introduced in Python 3.10.
-
E.
PEP 695
PEP 695 is a Python Enhancement Proposal that introduces a new, more concise syntax for type parameter declarations to improve the language’s support for generics and static typing.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: PEP 333 Target entity description: PEP 333 is the Python Enhancement Proposal that originally defined the Web Server Gateway Interface (WSGI), a standard for communication between Python web applications and web servers.
-
A.
PEP 634
PEP 634 is the Python Enhancement Proposal that formally specifies the semantics of structural pattern matching introduced in Python 3.10.
-
B.
PEP 622
PEP 622 is a Python Enhancement Proposal that introduced the design for structural pattern matching syntax later adopted in Python 3.10.
-
C.
PEP 636
PEP 636 is a Python Enhancement Proposal that serves as a tutorial-style guide to the structural pattern matching feature introduced in Python 3.10.
-
D.
PEP 635
PEP 635 is a Python Enhancement Proposal that provides a detailed rationale and motivation for the structural pattern matching feature introduced in Python 3.10.
-
E.
PEP 695
PEP 695 is a Python Enhancement Proposal that introduces a new, more concise syntax for type parameter declarations to improve the language’s support for generics and static typing.
- F. None of above. chosen
Statements (43)
| Predicate | Object |
|---|---|
| instanceOf | Python Enhancement Proposal ⓘ |
| abbreviation | WSGI ⓘ |
| aimsTo | promote web application portability across Python web servers ⓘ |
| author | Phillip J. Eby ⓘ |
| category |
Networking
ⓘ
Web ⓘ
linked to:
WEB
|
| context | Python web ecosystem in early 2000s ⓘ |
| created | 2003-09-12 ⓘ |
| defines |
I/O handling via input and error streams
ⓘ
Web Server Gateway Interface ⓘ
linked to:
WSGI
error handling conventions for WSGI ⓘ threading and process model considerations for WSGI ⓘ |
| definesTerm |
WSGI application
ⓘ
linked to:
WSGI
WSGI middleware ⓘ WSGI server ⓘ |
| ensures |
that a single WSGI application can run on multiple compliant servers
ⓘ
that middleware can be composed between servers and applications ⓘ |
| influenced |
Python web frameworks
ⓘ
Python web servers ⓘ middleware components in Python web stack ⓘ |
| inspired | standardization of Python web deployment practices ⓘ |
| language | Python ⓘ |
| motivation | unify various Python web framework and server interfaces ⓘ |
| partOf | Python PEP index ⓘ |
| relatedTo |
CGI
ⓘ
Common Gateway Interface ⓘ |
| repository | https://peps.python.org/pep-0333/ ⓘ |
| requires |
CGI-like environment variables
ⓘ
PEP 333-compliant server to invoke application callable ⓘ |
| specifies |
calling convention for Python web applications
ⓘ
environment variables for HTTP requests ⓘ iterable response body from applications ⓘ start_response callable semantics ⓘ |
| standardizes | interface between Python web servers and applications ⓘ |
| status | Final ⓘ |
| supersededBy |
PEP 3333
ⓘ
linked to:
PEP 333
|
| targetPythonVersion | Python 2 ⓘ |
| title |
Python Web Server Gateway Interface v1.0
ⓘ
linked to:
WSGI
|
| topic |
Python web applications
ⓘ
Python web servers ⓘ application server interface ⓘ |
| type |
Standards Track PEP
ⓘ
linked to:
Standards Track PEPs
|
| versionDefined |
WSGI 1.0
ⓘ
linked to:
WSGI
|
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: PEP 333 Description of subject: PEP 333 is the Python Enhancement Proposal that originally defined the Web Server Gateway Interface (WSGI), a standard for communication between Python web applications and web servers.
Referenced by (8)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: PEP 333
linked to: PEP 333
subject linked to:
Werkzeug WSGI utility library
linked to: PEP 333
linked to: PEP 333