HTML transcription functions.
Malformed markup is enraging. Therefore, when I must generate HTML I construct a token structure using natural Python objects (strings, lists, dicts) and use this module to transcribe them to syntacticly correct HTML. This also avoids lots of tediuous and error prone entity escaping.
tok2s: transcribe tokens to a string; trivial wrapper for puttok
puttok: transcribe tokens to a file
text2s: transcribe a string to an HTML-safe string; trivial wrapper for puttext
puttext: transcribe a string as HTML-safe text to a file
BR: a convenience token for <br/>, which I use a lot
A “token” in this scheme is:
a string: transcribed safely to HTML
an int or float: transcribed safely to HTML
a preformed token object with .tag (a string) and .attrs (a mapping) attributes
a sequence: an HTML tag: element 0 is the tag name, element 1 (if a mapping) is the element attributes, any further elements are enclosed tokens
because a string like “&foo” gets its “&” transcribed into the entity “&”, a single element list whose tag begins with “&” encodes an entity, example: [”<”]
Example:
from cs.html import puttoken, BR
[...]
table = ['TABLE', {'width': '80%'},
['TR',
['TD', 'a truism'],
['TD', '1 < 2']
]
]
[...]
puttoken(sys.stdout,
'Here is a line with a line break.', BR,
'Here is a trite table.',
table)
Metadata
Release files for cs.html 20150721
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 |
|---|---|---|---|---|
| cs.html-20150721.tar.gz | 4.3 kB | Without provenance | Details for cs.html-20150721.tar.gz |
Release files / cs.html-20150721.tar.gz
| Download URL | cs.html-20150721.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ed36eda20b526a03c9860d31646740ae0daf8953c9332ea5cde899b7debaf97
|
|
BLAKE2b-256 checksum How to use checksums |
864aff73b9e99b242aa1377ce6bbbacf6ad11ab1bb368b7ea1e7211b954341f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cs.html 20150721
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.