[https://bitbucket.org/userzimmermann/python-coffeetools]()
[coffee][1] interface for evaluating and compiling [CoffeeScript](http://coffeescript.org/)
[{% coffee … %}][2] template tags for [Jinja2](http://jinja.pocoo.org)
- [%%coffeescript][3] magic function for [IPython Notebook](
0. Setup
Supported Python versions: __2.7__ and __3.3+__
You need an installed CoffeeScript compiler. By default __coffeetools__ look for a coffee executable in your PATH, or coffee.cmd on Windows. You can find installation instructions and further information at [http://coffeescript.org/](). The easiest way is to use the [node package manager](https://www.npmjs.com/):
npm install coffee-script
To install __coffeetools__, just use [pip](http://www.pip-installer.org) to get the latest [release](https://pypi.python.org/pypi/coffeetools) from [PyPI](https://pypi.python.org):
pip install coffeetools
For basic usage there are no dependencies on other Python packages.
__Jinja__ and __IPython__ integration are [extra] features. They require the following Python packages:
[jinja]
[jinjatools >= 0.1.4](https://pypi.python.org/pypi/jinjatools)
[ipython]
[ipython[notebook]](https://pypi.python.org/pypi/ipython)
All extra Python requirements can also be installed with:
pip install coffeetools[all]
1. Using CoffeeScript from Python
[1]: #markdown-header-1-using-coffeescript-from-python
from coffeetools import coffee
Evaluate CoffeeScript code and return the script’s output:
coffee(‘Some CoffeeScript’)
Compile CoffeeScript to JavaScript:
coffee.compile(‘Some CoffeeScript’)
Compile CoffeeScript to JavaScript without a top-level function():
coffee.compile(‘Some CoffeeScript’, bare=True)
If you want to specify a custom name of your CoffeeScript compiler executable or its absolute or relative path, just create a custom interface instance:
from coffeetools import Coffee
coffee = Coffee(‘executable’) #OR coffee = Coffee(‘/absolute/path/to/executable’) #OR coffee = Coffee(‘relative/path/to/executable’)
2. Using CoffeeScript from Jinja2
[2]: #markdown-header-2-using-coffeescript-from-jinja2
More information coming soon…
3. Evaluate CoffeeScript in an IPython Notebook
[3]: #markdown-header-3-evaluate-coffeescript-in-an-ipython-notebook
%load_ext coffeescript
It is also safe to %reload_ext coffeescript
This registers the %%coffeescript cell magic function, which works like Ipython’s %%javascript magic, except that it takes CoffeeScript as input. It compiles the given code to JavaScript and uses IPython.display.display() with IPython.display.Javascript to run the code directly in the browser window:
%%coffeescript alert $(‘#notebook_name’).text()
Metadata
Release files for coffeetools 0.1.2
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 |
|---|---|---|---|---|
| coffeetools-0.1.2.tar.gz | 19.2 kB | Without provenance | Details for coffeetools-0.1.2.tar.gz |
Release files / coffeetools-0.1.2.tar.gz
| Download URL | coffeetools-0.1.2.tar.gz |
|---|---|
| Size | 19.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ff6078cf9724f892543f36e464afbb1eec9b2d303960ac85173aea659ffa8344
|
|
BLAKE2b-256 checksum How to use checksums |
adeed93593bda437620dbc5e3435f9b9771d018509486659f724596ef596b18d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for coffeetools 0.1.2
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.