Python binding for libsass
Usage
>>> import sass
>>> sass.compile_string("div { a { color: black}}")
'div a {\n color: black; }\n'Installation
pip install sassCompatibility
Tested with Python 2.7 and Python 3.2/3.3
Development
Steps to compile and install:
sudo pip install Cython
git submodule init
git submodule update
cd libsass
git submodule init
git submodule update
cd ..
make
sudo python setup.py developIf you want to use an alternate python, you’ll have to edit the Makefile or execute those commands from activated virtualenv.
How to contribute
It is easy. Fork repo on GitHub, fix stuff and send me nice looking pull-request.
1 maintainer
Metadata
1 maintainer
Release files for sass 2.3
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 |
|---|---|---|---|---|
| sass-2.3.tar.gz | 126.3 kB | Without provenance | Details for sass-2.3.tar.gz |
Release files / sass-2.3.tar.gz
| Download URL | sass-2.3.tar.gz |
|---|---|
| Size | 126.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c7e7475ffc6eaadc510516c76cfdb86aaed9b981ff41c2fd1543030bee26332b
|
|
BLAKE2b-256 checksum How to use checksums |
9de6fa54218308bc2fc4994010513dd3a4078c7f8fc791d50fa033d9fd91c1f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sass 2.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.
