Skip to main content
Help us improve PyPI by participating in user testing. All experience levels needed!

SASS processor to compile SCSS files into *.css, while rendering, or offline.

Project description


Being annoyed having to run a Compass, Grunt or Gulp daemon while
developing Django projects?

Well, then this app is for you! Compile SASS/SCSS files on the fly
without having to manage third party services nor special IDE plugins.

Other good reasons for using this library

From now on, you refer SASS/SCSS files directly from your sources,
instead of referring a compiled CSS file, hoping that some other utility
will create it from a SASS/SCSS file, hidden somewhere in your source

Use Django's settings for the configuration of pathes, box sizes etc.,
instead of having another SCSS specific file (typically
``_variables.scss``), to hold these.

Extend your SASS functions by calling Python functions directly out of
your Django project.

|Build Status| |PyPI| |PyPI version| |PyPI| |Twitter Follow|

**django-sass-processor** converts ``*.scss`` or ``*.sass`` files into
``*.css`` while rendering templates. For performance reasons this is
done only once, since the preprocessor keeps track on the timestamps and
only recompiles, if any of the imported SASS/SCSS files is younger than
the corresponding generated CSS file.


This Django app provides a templatetag
``{% sass_src 'path/to/file.scss' %}``, which can be used instead of the
built-in templatetag ``static``. This templatetag also works inside
Jinja2 templates.

If SASS/SCSS files shall be referenced through the ``Media`` class, or
``media`` property, the SASS processor can be used directly.

Additionally, **django-sass-processor** is shipped with a management
command, which can convert the content of all occurrences inside the
templatetag ``sass_src`` as an offline operation. Hence the **libsass**
compiler is not required in a production environment.

During development, a
`sourcemap <>`__
is generated along side with the compiled ``*.css`` file. This allows to
debug style sheet errors much easier.

With this tool, you can safely remove your Ruby installations "Compass"
and "SASS" from your Django projects. You neither need any directory
"watching" daemons based on node.js.

Project's Home

On GitHub:

Please use the issue tracker to report bugs or propose new features.



pip install libsass django-compressor django-sass-processor

``django-compressor`` is required only for offline compilation, when
using the command `` compilescss``.

``libsass`` is not required on the production environment, if SASS/SCSS
files have been precompiled and deployed using offline compilation.


In ```` add to:

.. code:: python


Optionally, add a list of additional search paths, the SASS compiler may
examine when using the ``@import "...";`` statement in SASS/SCSS files:

.. code:: python

import os

os.path.join(PROJECT_PATH, 'extra-styles/scss'),
os.path.join(PROJECT_PATH, 'node_modules'),

Additionally, **django-sass-processor** will traverse all installed
Django apps (``INSTALLED_APPS``) and look into their static folders. If
any of them contain a file matching the regular expression pattern
``^_.+\.(scss|sass)$`` (read: filename starts with an underscore and is
of type ``scss`` or ``sass``), then that app specific static folder is
added to the **libsass** include dirs. This feature can be disabled in
your settings with:

.. code:: python


If inside of your SASS/SCSS files, you also want to import (using
``@import "path/to/scssfile";``) files which do not start with an
underscore, then you can configure another Regex pattern in your
settings, for instance:

.. code:: python


will look for all files of type ``scss``. Remember that SASS/SCSS files
which start with an underscore, are intended to be imported by other
SASS/SCSS files, while files starting with a letter or number are
intended to be included by the HTML tag
``<link href="{% sass_src 'path/to/file.scss' %}" ...>``.

During development, or when ``SASS_PROCESSOR_ENABLED = True``, the
compiled file is placed into the folder referenced by
``SASS_PROCESSOR_ROOT`` (if unset, this setting defaults to
``STATIC_ROOT``). Having a location outside of the working directory
prevents to pollute your local ``static/css/...`` directories with
auto-generated files. Therefore assure, that this directory is writable
by the Django runserver.

**django-sass-processor** is shipped with a special finder, to locate
the generated ``*.css`` files in the directory referred by
``SASS_PROCESSOR_ROOT`` (or, if unset ``STATIC_ROOT``). Just add it to
your ````. If there is no ``STATICFILES_FINDERS`` in your
```` don't forget to include the **Django** `default
finders <>`__.

If the directory referred by ``SASS_PROCESSOR_ROOT`` does not exist,
then **django-sass-processor** creates it. This does does not apply, if
``SASS_PROCESSOR_ROOT`` is unset and hence defaults to ``STATIC_ROOT``.
Therefore it is a good idea to otherwise use

.. code:: python


Fine tune SASS compiler parameters in ````.

Integer ``SASS_PRECISION`` sets floating point precision for output css.
libsass' default is ``5``. Note: **bootstrap-sass** requires ``8``,
otherwise various layout problems *will* occur.

.. code:: python


``SASS_OUTPUT_STYLE`` sets coding style of the compiled result, one of
``compact``, ``compressed``, ``expanded``, or ``nested``. Default is
``nested`` for ``DEBUG`` and ``compressed`` in production.

Note: **libsass-python** 0.8.3 has `problem encoding result while saving
on Windows <>`__, the
issue is already fixed and will be included in future ``pip`` package
release, in the meanwhile avoid ``compressed`` output style.

.. code:: python


Jinja2 support

``sass_processor.jinja2.ext.SassSrc`` is a Jinja2 extension. Add it to
your Jinja2 environment to enable the tag ``sass_src``, there is no need
for a ``load`` tag. Example of how to add your Jinja2 environment to

In ````:

.. code:: python

'BACKEND': 'django.template.backends.jinja2.Jinja2',
'DIRS': [],
'APP_DIRS': True,
'environment': 'yourapp.jinja2.environment'

Make sure to add the default template backend, if you're still using
Django templates elsewhere. This is covered in the `Upgrading templates
documentation <>`__.

In ``yourapp/``:

.. code:: python

# Include this for Python 2.
from __future__ import absolute_import

from jinja2 import Environment

def environment(**kwargs):
extensions = [] if 'extensions' not in kwargs else kwargs['extensions']
kwargs['extensions'] = extensions

return Environment(**kwargs)

If you want to make use of the ``compilescss`` command, then you will
also have to add the following to your settings:

.. code:: python

from yourapp.jinja2 import environment



In your Django templates

.. code:: django

{% load sass_tags %}

<link href="{% sass_src 'myapp/css/mystyle.scss' %}" rel="stylesheet" type="text/css" />

The above template code will be rendered as HTML

.. code:: html

<link href="/static/myapp/css/mystyle.css" rel="stylesheet" type="text/css" />

You can safely use this templatetag inside a Sekizai's
``{% addtoblock "css" %}`` statement.

In Media classes or properties

In Python code, you can access the API of the SASS processor directly.
This for instance is useful in Django's admin or form framework.

.. code:: python

from sass_processor.processor import sass_processor

class SomeAdminOrFormClass(...):
class Media:
css = {
'all': [sass_processor('myapp/css/mystyle.scss')],

Add vendor prefixes to CSS rules using values from

Writing SCSS shall be fast and easy and you should not have to care,
whether to add vendor specific prefixes to your CSS directives.
Unfortunately there is no pure Python package to solve this, but with a
few node modules, we can add this to our process chain.

As superuser install

.. code:: shell

npm install -g npx

and inside your project root, install

.. code:: shell

npm install postcss-cli autoprefixer

Check that the path of ``node_modules`` corresponds to its entry in the
settings directive ``STATICFILES_DIRS`` (see below).

In case ``npx`` can not be found in your system path, use the settings
directive ``NODE_NPX_PATH = /path/to/npx`` to point to that executable.

If everything is setup correctly, **django-sass-processor** adds all
required vendor prefixes to the compiled CSS files. For further
information, refer to the
`Autoprefixer <>`__ package.

To disable autoprefixing, set ``NODE_NPX_PATH = None``.

**Important note**: If ``npx`` is installed, but ``postcss`` and/or
``autoprefixer`` are missing in the local ``node_modules``, setting
``NODE_NPX_PATH`` to ``None``\ is manadatory, otherwise
**django-sass-processor** does not know how to postprocess the generated
CSS files.

Offline compilation

If you want to precompile all occurrences of your SASS/SCSS files for
the whole project, on the command line invoke:

.. code:: shell

./ compilescss

This is useful for preparing production environments, where SASS/SCSS
files can't be compiled on the fly.

To simplify the deployment, the compiled ``*.css`` files are stored
side-by-side with their corresponding SASS/SCSS files. After compiling
the files run

.. code:: shell

./ collectstatic

as you would in a normal deployment.

In case you don't want to expose the SASS/SCSS files in a production
environment, deploy with:

.. code:: shell

./ collectstatic --ignore=*.scss

To get rid of the compiled ``*.css`` files in your local static
directories, simply reverse the above command:

.. code:: shell

./ compilescss --delete-files

This will remove all occurrences of previously generated ``*.css``

Or you may compile results to the ``SASS_PROCESSOR_ROOT`` directory
directy (if not specified - to ``STATIC_ROOT``):

.. code:: shell

./ compilescss --use-processor-root

Combine with ``--delete-files`` switch to purge results from there.

If you use an alternative templating engine set its name in ``--engine``
argument. Currently ``django`` and ``jinja2`` are supported, see
documentation <>`__
on how to set up ``COMPRESS_JINJA2_GET_ENVIRONMENT`` to configure jinja2
engine support.

During offline compilation **django-sass-processor** parses all Python
files and looks for invocations of
``sass_processor('path/to/sassfile.scss')``. Therefore the string
specifying the filename must be hard coded and shall not be concatenated
or being somehow generated.

Alternative templates

By default, **django-sass-processor** will locate SASS/SCSS files from
.html templates, but you can extend or override this behavior in your
settings with:

.. code:: python

SASS_TEMPLATE_EXTS = ['.html','.jade']

Configure SASS variables through

In SASS, a nasty problem is to set the correct include paths for icons
and fonts. Normally this is done through a ``_variables.scss`` file, but
this inhibits a configuration through your projects ````.

To avoid the need for duplicate configuration settings,
**django-sass-processor** offers a SASS function to fetch any arbitrary
configuration directive from the project's ````. This is
specially handy to set the include path of your Glyphicons font
directory. Assume, Bootstrap-SASS has been installed using:

.. code:: shell

npm install bootstrap-sass

then locate the directory named ``node_modules`` and add it to your
settings, so that your fonts are accessible through the Django's

.. code:: python

('node_modules', '/path/to/your/project/node_modules/'),

NODE_MODULES_URL = STATIC_URL + 'node_modules/'

With the SASS function ``get-setting``, it is possible to override any
SASS variable with a value configured in the project's ````.
For the Glyphicons font search path, add this to your

.. code:: scss

$icon-font-path: unquote(get-setting(NODE_MODULES_URL) + "bootstrap-sass/assets/fonts/bootstrap/");

and ``@import "variables";`` whenever you need Glyphicons. You then can
safely remove any font references, such as
``<link href="/path/to/your/fonts/bootstrap/glyphicons-whatever.ttf" ...>``
from you HTML templates.

It is even possible to call Python functions from inside any module. Do
this by adding ``SASS_PROCESSOR_CUSTOM_FUNCTIONS`` to the project's
````. This shall contain a mapping of SASS function names
pointing to a Python function name.


.. code:: python

'get-color': 'myproject.utils.get_color',

.. code:: scss

$color: get-color(250, 10, 120);

This will pass the parameters '250, 10, 120' into the function
``def get_color(red, green, blue)`` in Python module
``myproject.utils``. Note that this function receives the values as
``sass.Number``, hence extract values using ``red.value``, etc.

If one of these customoized functions returns a value, which is not a
string, then convert it either to a Python string or to a value of type
``sass.SassNumber``. For other types, refer to their documentation.

Such customized functions must accept parameters explicilty, otherwise
``sass_processor`` does not know how to map them. Variable argument
lists therefore can not be used.

Serving static files with S3

A custom Storage class is provided for use if your deployment serves css
files out of S3. You must have Boto 3 installed. To use it, add this to
your settings file:




To run the tests locally, clone the repository, create a new virtualenv,
activate it and then run these commands:

.. code:: shell

cd django-sass-processor
pip install tox


- 0.7

- Allow to call directly into Python functions.

- 0.6

- Add autoprefixing via external postcss.

- 0.5.8

- *Potentially Breaking*: ``libsass`` is not autoinstalled as the
dependency anymore.
- Add support for Django-2.0.

- 0.5.7

- Fixed: Catch exception if s3boto is not installed.

- 0.5.6

- Added compatibility layer to work with AWS S3 Storage.

- 0.5.5

- Create directory ``SASS_PROCESSOR_ROOT`` if it does not exist.

- 0.5.4

- Added unit tests and continuous integration to the project.

- 0.5.3

- Fixed compilescss: Did not find calls of sass\_processor within a
dict, list or tuple

- 0.5.2

- Fixed Python 3 incompatibility. Open files as binaries, since they
may contain unicode characters.

- 0.5.1

- Add ``APPS_INCLUDE_DIRS`` to the SASS include path.

- 0.5.0

- SASS/SCSS files can also be referenced in pure Python files, for
instance in ``Media`` class or ``media`` property definitions.
- The SASS processor will look for potential include directories, so
that the ``@import "..."`` statement also works for SASS files
located in other Django apps.

- 0.4.0 - 0.4.4

- Refactored the sass processor into a self-contained class
``SassProcessor``, which can be accessed through an API, the Jinja2
template engine and the existing templatetag.

- 0.3.5

- Added Jinja2 support, see `Jinja2 support <#jinja2-support>`__.

- 0.3.4

- Fixed: ``get_template_sources()`` in Django-1.9 returns Objects
rather than strings.
- In command, use ``ArgumentParser`` rather than ``OptionParser``.

- 0.3.1...0.3.3

- Changed the build process in ````.

- 0.3.0

- Compatible with Django 1.8+.
- bootstrap3-sass ready: appropriate floating point precision (8) can
be set in ````.
- Offline compilation results may optionally be stored in

- 0.2.6

- Hotfix: added SASS function ``get-setting`` also to offline compiler.

- 0.2.5

- Compatible with Python3
- Replaced ``SortedDict`` with ``OrderedDict`` to be prepared for
- Raise a ``TemplateSyntax`` error, if a SASS ``@include "..."`` fails
to find the file.
- Added SASS function ``get-setting`` to fetch configuration directives
from ````.

- 0.2.4

- Forcing compiled unicode to bytes, since 'Font Awesome' uses Unicode
Private Use Area (PUA) and hence implicit conversion on
``fh.write()`` failed.

- 0.2.3

- Allow for setting template extensions and output style.
- Force Django to calculate template\_source\_loaders from
TEMPLATE\_LOADERS settings, by asking to find a dummy template.

- 0.2.0

- Removed dependency to **django-sekizai** and **django-classy-tags**.
It now can operate in stand-alone mode. Therefore the project has
been renamed to **django-sass-processor**.

- 0.1.0

- Initial revision named **django-sekizai-processors**, based on a
preprocessor for the Sekizai template tags ``{% addtoblock %}``.

.. |Build Status| image::
.. |PyPI| image::
.. |PyPI version| image::
:target: https://
.. |PyPI| image::
.. |Twitter Follow| image::

Project details

Release history Release notifications

This version
History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


History Node


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Filename, size & hash SHA256 hash help File type Python version Upload date
django-sass-processor-0.7.tar.gz (25.8 kB) Copy SHA256 hash SHA256 Source None May 6, 2018

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging CloudAMQP CloudAMQP RabbitMQ AWS AWS Cloud computing Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page