Remove .pyc and __pycache__ in make clean

.gitignore

@@ -20,6 +20,9 @@
/share
/src

# All minified javascript is built
*.min.js

*.pyc
*.pyo

Makefile

@@ -7,20 +7,19 @@ default:
clean:
	@rm -rf h/static/.sass-cache
	@rm -rf h/static/.webassets-cache
	find h/static/scripts \
		-path 'h/static/scripts/vendor' -prune \
		-o -iname '*.js' \
		-exec rm {} \;
	find h/static/styles/*.css \
		-iname 'icomoon.css' -prune \
		-o -exec rm {} \;
	find . -type f -name "*.py[co]" -delete
	find . -type d -name "__pycache__" -delete
	find h/static/scripts -mindepth 1 -name '*.min.js' \
		-delete
	find h/static/styles -mindepth 1 \
		-name 'icomoon.css' -prune \
		-o -name '*.css' -delete

test:
	@echo -n "Checking to see if elasticsearch is running..."
	$(eval es := $(shell wget --quiet --output-document - http://localhost:9200))
	@if [ -n '${es}' ] ; then echo "yes." ; else echo "no!"; exit 1; fi
	python setup.py develop test
	hypothesis assets development.ini
	"$$(npm bin)"/karma start karma.config.js --single-run
	"$$(npm bin)"/karma start h/browser/chrome/karma.config.js --single-run

README.rst

@@ -107,10 +107,8 @@ To run the Python suite, invoke the tests in the standard fashion::

    $ ./bin/python setup.py test

To run the JavaScript suite, ensure the assets are built and then invoke the
karma test runner::
To run the JavaScript suite, run::

    $ hypothesis assets development.ini
    $ $(npm bin)/karma start karma.config.js --single-run

As a convenience, there is a make target which will do all of the above::
@@ -120,8 +118,7 @@ As a convenience, there is a make target which will do all of the above::
It's also possible to run a subset of the tests using ``karma run``::

    $ $(npm bin)/karma start karma.config.js & # Start the server in the bg.
    $ hypothesis assets development.ini && \
      $(npm bin)/karma run karma.config.js -- --grep={FILTER_STRING}
    $ $(npm bin)/karma run karma.config.js -- --grep={FILTER_STRING}

This will run generally be much faster than running ``karma start --single-run``
each time. The frontend tests can also be debugged by visiting

development.ini

@@ -47,13 +47,12 @@ jinja2.extensions: h.jinja_extensions:IncludeRawExtension

webassets.base_dir: h:static
webassets.base_url: assets
webassets.coffee_no_bare: True
webassets.debug: True
webassets.manifest: False
webassets.static_view: True
webassets.uglifyjs_bin: %(here)s/node_modules/.bin/uglifyjs
webassets.cleancss_bin: %(here)s/node_modules/.bin/cleancss
webassets.coffee_bin: %(here)s/node_modules/.bin/coffee
webassets.browserify_pipe_bin: %(here)s/tools/browserify-pipe

;http://docs.pylonsproject.org/projects/pyramid-debugtoolbar/en/latest/#settings
debugtoolbar.show_on_exc_only: True

h/assets.py

@@ -2,9 +2,41 @@
import re

from deform.field import Field
from webassets.filter import ExternalTool, register_filter
import pyramid


class Browserify(ExternalTool):
    """
    An input filter for webassets that browserifies CoffeeScript or JavaScript.

    The browserify command-line client has several limitations when piping
    input to STDIN:

    - it uses a dummy name for the piped file in sourcemaps
    - because it does not know the real name of the piped file, it cannot
      accept CoffeeScript, because it does not know the real extension of the
      piped file

    The filter uses the browserify-pipe tool, shipped in ``tools/`` in the
    repository root, which circumvents these issues.
    """
    name = 'browserify'
    options = {'binary': 'BROWSERIFY_PIPE_BIN'}
    max_debug_level = None

    def input(self, in_, out, source_path, **kwargs):
        args = [self.binary or 'browserify-pipe']

        if self.get_config('debug'):
            args.append('-d')

        args.append(source_path)
        self.subprocess(args, out, in_)

register_filter(Browserify)


class WebassetsResourceRegistry(object):

    def __init__(self, env):