This release is a pre-release and may not be stable for production use.
This package provides a framework to convert a string from one format, such as Structured or Restructured Text, to another, such as HTML. Converters are looked up by adapter and uses other packages to implement the converters.
CHANGES
4.0.0a1 (2013-03-01)
Renamed package from zope.app.renderer to zope.renderer.
Added support for Python 3.3.
Replaced deprecated zope.interface.implements usage with equivalent zope.interface.implementer decorator.
Dropped support for Python 2.4 and 2.5.
3.5.1 (2009-07-21)
Require the new roman package, since docutils does not install it correctly.
3.5.0 (2009-01-17)
Adapted to docutils 0.5 for ReST rendering: get rid of the ZopeTranslator class, because docutils changed the way it uses translator so previous implementation doesn’t work anymore. Instead, use publish_parts and join needed parts in the render method of the renderer itself.
Removed deprecated meta.zcml stuff and zpkg stuff.
Replaced __used_for__ with zope.component.adapts calls.
3.4.0 (2007-10-27)
Initial release independent of the main Zope tree.
1 maintainer
Metadata
1 maintainer
Release files for zope.renderer 4.0.0a1
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 | Actions |
|---|---|---|---|---|
| zope.renderer-4.0.0a1.zip | 20.6 kB | Without provenance | Details for zope.renderer-4.0.0a1.zip |
Release files / zope.renderer-4.0.0a1.zip
| Download URL | zope.renderer-4.0.0a1.zip |
|---|---|
| Size | 20.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
969098fc532fa3b694864ebbdaadb10d9b906ce0a8587e128aef32c1ff640e34
|
|
BLAKE2b-256 checksum How to use checksums |
cc84fa442772ea9cb4995153feaf8ebc99cd082f2b50d61e23c6a938d077fe62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for zope.renderer 4.0.0a1
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.
