root/alpine313/: legacy-cgi-2.6.3 metadata and description
Fork of the standard library cgi and cgitb modules removed in Python 3.13
| author_email | Guido van Rossum <guido@python.org>, Andreas Paepcke <paepcke@haddock.stanford.edu>, Steve Majewski <sdm7g@virginia.edu>, Michael McLay <mclay@eeel.nist.gov> |
| description_content_type | text/x-rst |
| license_expression | PSF-2.0 |
| license_file |
|
| maintainer_email | Jack Rosenthal <jack@rosenth.al> |
| metadata_version | 2.4 |
| project_urls |
|
| requires_python | >=3.8 |
| File | Tox results | History |
|---|---|---|
legacy_cgi-2.6.3-py3-none-any.whl
|
|
This is a fork of the standard library modules cgi and cgitb. They have been removed from the Python standard libary in Python 3.13 by PEP-594.
Installation
Depend upon legacy-cgi in your project. It is recommended to use the marker python_version >= 3.13, as while the package can install for older Python versions, it won’t have effect with a standard Python installation as the built-in modules will take precedence.
For example, in a requirements.txt file:
legacy-cgi; python_version >= '3.13'
Or in a PEP-621 pyproject.toml file:
[project]
...
dependencies = [
...,
"legacy-cgi; python_version >= '3.13'",
]
Purpose
The purpose of this fork is to support existing CGI scripts using these modules. Thus, compatibility is the primary goal.
Contributions are accepted, but should be focused on bug fixes instead of new features or major refactoring.
New applications should look at the ASGI or WSGI ecosystems. There’s a number of highly-polished web frameworks available, and it’s significantly faster in a typical deployment given a new Python process does not need created for each request.
Documentation
See the official documentation for Python 3.12 and earlier for usage:
The modules are not renamed, so code written for Python 3.12 or earlier should work without modification with this package installed.