About tgext.less
LESS is a dynamic stylesheet language that extends CSS with dynamic behaviour such as variables, mixins, operations and functions.
tgext.less is a middleware aimed at making TurboGears2 development easier, tgext.less converts regular less files to css using the official less compiler (lessc), thus it currently requires is to be installed.
tgext.less is based on tgext.scss by Alessandro Molina and is under the same license (MIT).
Installing
tgext.less can be installed both from pypi or from bitbucket:
easy_install tgext.less
You will also need to install the less compiler, for instructions on this check the less website under the server side usage section.
Enabling tgext.less
Using tgext.less is really simple, you edit your config/middeware.py and just after the #Wrap your base TurboGears 2 application with custom middleware here comment wrap app with LESSMiddleware:
from tgext.less import LESSMiddleware
make_base_app = base_config.setup_tg_wsgi_app(load_environment)
def make_app(global_conf, full_stack=True, **app_conf):
app = make_base_app(global_conf, full_stack=True, **app_conf)
# Wrap your base TurboGears 2 application with custom middleware here
app = LESSMiddleware(app)
return app
Now you just have to put your .less files inside public/css and they will be served as CSS.
Cache Backends
You can change the cache backend storage into any dict like object that can serialize a dict object, for example, you can use beaker cache by passing the cache object to the middleware constructor:
from tgext.less import LESSMiddleware
from tg import cache
make_base_app = base_config.setup_tg_wsgi_app(load_environment)
def make_app(global_conf, full_stack=True, **app_conf):
app = make_base_app(global_conf, full_stack=True, **app_conf)
# LESS with beaker cache backend
app = LESSMiddleware(app, cache=cache)
return app
Jinja2 Extension
tgext.less provides and extension for jinja2 templates to compile LESS embedded directly on your templates, to activate it just add it to your config/app_config.py file the following:
from tgext.less.jinja import LessExtension base_config.jinja_extensions = [LessExtension]
Now you can use the less tag in your templates:
<style type="text/css">
{% less "main" %}
#header {
h1 {
font-size: 24pt;
}
}
{% endless %}
</style>
Where “main” is a unique identifier for that LESS section.
You should take into account that when using mixins or any other identifier not defined inside the tag the LESS code will fail to compile, you can use the @import statement to include a file, in which case you should include the path relative to your static file directory:
<style type="text/css">
{% less "main" %}
@include "css/bootstrap.less";
#round_box {
.border-radius(5px);
}
{% endless %}
</style>
You should be aware that when using this extension with the LESS import statement the output can get big quickly as the compiler currently does not just get the necessary things from the imported file but it just naively includes the whole file (as in the example, the while bootstrap library will be included).
Metadata
Release files for tgext.less 0.3.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 |
|---|---|---|---|---|
| tgext.less-0.3.1.tar.gz | 4.3 kB | Without provenance | Details for tgext.less-0.3.1.tar.gz |
Release files / tgext.less-0.3.1.tar.gz
| Download URL | tgext.less-0.3.1.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d20a10719cf9e0cc3ea79cd3fb50b723a8815aaff7ce68a1bea3523799d44772
|
|
BLAKE2b-256 checksum How to use checksums |
7da3c35e4bdc5eff39420b0e58b043c57978f9151a4c57917e21e20456b35c5d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for tgext.less 0.3.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.