Skip to main content

HTMLer

HTMLer is a simple HTML generation library for Python.

Build status

Build Status Coverage

Features

  • Easy and flexible to use.
  • Outputs beautifully indented code

Requirements

Python >=3.6

Installation

pip install htmler

Usage

This example:

from htmler import Html, Head, Body, Meta, Title, Script, Link, P, A

doc = Html(
    Head(
        Meta(charset='utf-8'),
        Title('Hello World Document'),
        Script(src='main.js'),
        Link(rel='stylesheet', src='main.css'),
    ),
    Body(
        P(
            A('Hello World!', href="https://en.wikipedia.org/wiki/%22Hello,_World!%22_program")
        )
    ),
    lang="en",
)

print(doc)

will provide following output:

<!DOCTYPE html>
<html lang="en">
    <head>
        <meta charset="utf-8">
        <title>
            Hello World Document
        </title>
        <script src="main.js"></script>
        <link rel="stylesheet" src="main.css">
    </head>
    <body>
        <p>
            <a href="https://en.wikipedia.org/wiki/%22Hello,_World!%22_program">Hello World!</a>
        </p>
    </body>
</html>

If indentation is not necessary, just call render() method with indent argument set to False:

print(doc.render(indent=False))

Documentation

Work in progress.

Testing

python setup.py test

or

make test

Contributing

If you want to contribute to a project and make it better, your help is very welcome. Contributing is also a great way to learn more about social coding on Github, new technologies and and their ecosystems and how to make constructive, helpful bug reports, feature requests and the noblest of all contributions: a good, clean pull request.

  • Create a personal fork of the project on Github.
  • Clone the fork on your local machine. Your remote repo on Github is called origin.
  • Add the original repository as a remote called upstream.
  • If you created your fork a while ago be sure to pull upstream changes into your local repository.
  • Create a new branch to work on. Branch from develop if it exists, else from master.
  • Implement/fix your feature, comment your code.
  • Follow the code style of the project, including indentation.
  • If the project has tests run them.
  • Write or adapt tests as needed.
  • Add or change the documentation as needed.
  • Squash your commits into a single commit with git's interactive rebase. Create a new branch if necessary.
  • Push your branch to your fork on Github, the remote origin.
  • From your fork open a pull request in the correct branch. Target the project's develop branch if there is one, else go for master.
  • If the maintainer requests further changes just push them to your branch.
  • Once the pull request is approved and merged you can pull the changes from upstream to your local repo and delete your extra branch(es).

And last but not least: Always write your commit messages in the present tense. Your commit message should describe what the commit, when applied, does to the code – not what you did to the code.

Roadmap

  • Write documentation.

Support

If you have any issues or enhancement proposals feel free to report them via project's Issue Tracker.

Authors

Credits

This project was inspired by PyHTML library.

License

This project is licensed under the MIT License. See the LICENSE.md file for details.

Metadata

Release files for htmler 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for htmler 0.1.3
File Interpreter ABI Platform Actions
htmler-0.1.3-py3-none-any.whl Python 3 none any Details for htmler-0.1.3-py3-none-any.whl

Release files / htmler-0.1.3-py3-none-any.whl

Download URL htmler-0.1.3-py3-none-any.whl
Size 10.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a8c9c80014204f00d375283b33d0fb749758fda613b72ca1fea836ead1a430ae
BLAKE2b-256 checksum
How to use checksums
c6dd7ab507bb88048e54b99a6af100472bb73f0b8fae30e74ea2641db97a9735
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.28.1 CPython/3.7.3

Security for htmler 0.1.3

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page