Welcome to phtml !
phtml is a silly python library to generate HTML in Python like you would with a template, but refactor-oriented with a Pythonic React-like pattern based on nested components.
Component base
The base component class is Node:
from phtml import Node
form_layout = Node(
'form', # node.tag
{ # node.attrs
'class': 'foo', # node.attrs['class']
'method': 'POST', # node.attrs['method']
},
[ # node.children
'{{ form.as_p() }}', # node.children[0]
Node('input', {'type': 'submit'}, selfclose=True),
],
)
Casting form_layout to string will return the following:
<form class="foo" method="POST">
{{ form.as_p() }}
<input type="submit" />
</form>
Rendering
While calling phtml.jinja.render(form_layout, form=YourForm()) will return the phtml output processed with form in the context and produce the final result.
The whole purpose is refactoring HTML generating logic into Python components:
from phtml import Form, Submit
form_layout = Form(
{'class': 'foo'},
['{{ form.as_p() }}', Submit())],
)
Importing on the fly
from phtml import Node
form_layout = Node.factory(
'phtml.Form', {'class': 'foo'},
['{{ form.as_p() }}', Node('phtml.Submit')],
)
Jinja and Materialize for the poor
Suppose you want to make a nice layout for the login form, please don’t repeat boring and verbose code like this because somewhere in the world a cat would probably die because of a side effect in an alternate reality or something:
from phtml import Form, Div
your_layout = Form(
Div({'class': 'row'}, [
Div({'class': 'col m6 s12'}, ['{{ form["username"] }}']),
Div({'class': 'col m6 s12'}, ['{{ form["password"] }}']),
]),
)
Refactored components for the rich
Instead make a beautiful layout with reusable components:
from phtml.django.mdc import Form, Row, Col, Input
class YourLoginForm(forms.LoginForm):
_phtml = Form(
Row(
Col(m=6, s=12, Input('username')),
Col(m=6, s=12, Input('password')),
)
)
Silly and Stupid context based rendering
You could render as such in jinja (or in Python without the curly braces): {{ form._phtml.jinja(form) }}, since all rendering logic should already be in phtml.
Thank you
Thanks a lot for reading. Hope this will serve as a useful example for anybody on a mission to “refactor HTML in Python”.
Metadata
Release files for phtml 0.0.1
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 |
|---|---|---|---|---|
| phtml-0.0.1.tar.gz | 4.0 kB | Without provenance | Details for phtml-0.0.1.tar.gz |
Release files / phtml-0.0.1.tar.gz
| Download URL | phtml-0.0.1.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c8503b1ecdf4a67fd31ba7f43d7b6de18ce7c249ca279aefa0dab2a9342f61e8
|
|
BLAKE2b-256 checksum How to use checksums |
c82f9c2ff4317d3f0bd773273aba4e0f96036f66b85212038882ee17df39253e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for phtml 0.0.1
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.