zope.structuredtext
This package provides a parser and renderers for the classic Zope “structured text” markup dialect (STX). STX is a plain text markup in which document structure is signalled primarily by indentation
Please see https://zopestructuredtext.readthedocs.org/ for documentation.
Changes
6.0 (2025-09-12)
Replace pkg_resources namespace with PEP 420 native namespace.
5.1 (2025-08-11)
Add support for Python 3.12, 3.13.
Add support for Sphinx 8.
Drop support for Python 3.7, 3.8.
5.0 (2023-05-09)
Drop support for Python 2.7, 3.5, 3.6.
Drop support for deprecated python setup.py test.
Add support for Python 3.11.
4.4 (2022-03-18)
Add support for Python 3.8, 3.9 and 3.10.
Drop support for Python 3.4.
4.3 (2018-10-09)
Add support for Python 3.7.
4.2.0 (2017-09-05)
Add support for Python 3.5 and 3.6.
Drop support for Python 2.6 and 3.3.
Add support for PyPy and PyPy3.
Support several new elements (inner and named links, underlines, etc) in the docbook writer.
Fix the XML output of DocBookBook.
100% test coverage, maintained by CI and tox.
Unused internal code in the stdom module was removed. See issue 3.
4.1.0 (2014-12-29)
Drop dependency on six.
Add support for Python 3.4.
Add support for testing on Travis.
4.0.0 (2013-02-25)
Add support for Python 3.3.
Drop support for Python 2.4 and 2.5.
3.5.1 (2010-12-03)
Remove antique copyright assertions in regression texts, in conformance with repository policy.
3.5.0 (2010-04-30)
Update docs to conform to ZTK / Sphinx usage.
LP #120376: Output valid html for non-ASCII characters.
3.4.0 (2007/09/01)
Public release for completeness of Zope 3.4.
3.2.0 (2006/01/05)
Corresponds to the verison of the zope.structuredtext package shipped as part of the Zope 3.2.0 release.
Only coding style / documentation changes.
3.0.0 (2004/11/07)
Corresponds to the verison of the zope.structuredtext package shipped as part of the Zope X3.0.0 release.
Metadata
Release files for zope.structuredtext 6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| zope_structuredtext-6.0.tar.gz | 74.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zope_structuredtext-6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 166.9 kB
Release files / zope_structuredtext-6.0.tar.gz
| Download URL | zope_structuredtext-6.0.tar.gz |
|---|---|
| Size | 74.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3ec31e22459711dde25e0ee3dc744f2cb70ac77ab090776a11a901db4b7ab94f
|
|
BLAKE2b-256 checksum How to use checksums |
3fd7d3770b41215d754beebddd9286fd39aecfcd3355c3cfd8161024c3aba8f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Release files / zope_structuredtext-6.0-py3-none-any.whl
| Download URL | zope_structuredtext-6.0-py3-none-any.whl |
|---|---|
| Size | 92.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a62999493901d840b100dd19ec2f1a6de4aa608e93dd0cb4cc7a83272ec015a2
|
|
BLAKE2b-256 checksum How to use checksums |
3641a37ac4c1b5d5047a6810136a4ce931a937f2856889c7e23bc2fd1d5ed602
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Security for zope.structuredtext 6.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
