Turn off automatic snapshot to tmp dir on lettuce failure

Add comment to dynamically-generated asset files

To avoid confusion about where these files come from, add a header
comment upon preprocessing that warns people to not modify the
generated files directly, and points them to the appropriate
template file.

Peter fogg/single click video creation

adding sympy and networkx

Fix bug STUD-103. The url base for about page links needs to be www.edx....

Studio - Advanced Component Icon

Fix/btalbot/edx.org accessibility

edx.org - revises login and register graphical banner images to include higher contrast between type and imagery

Prevent creation of unnecessary template divs, and rename .single_templates to .single-templates for convention.

Fix bug STUD-103. The url base for about page links needs to be www.edx.org for Drupal site, vs. LMS_BASE which is used for Studio. Note that the complete URL is still not correct, but a redirect exists to take it to the new location.

Ned/move loncapa etc into sandbox

Install steps - Fixes syntax of `update_templates` django command

Jonahstanley/add more tests

Preprocess assets as Django management command

Added requirement for pip>=1.3

Using `task()` reopens the definition of the task, and all we really
need to do is get a reference to the task itself to invoke it.

The :browse_jasmine_<system> and :phantomjs_jasmine_<system> tasks
depend on the :assets task, which needs to receive both :system and
:env arguments. Therefore, new tasks (:browse_jasmine and
:phantomjs_jasmine) are created that do take :system and :env args.
The old :browse_jasmine_<system> and :phantomjs_jasmine_<system>
tasks now wrap the new tasks, passing in <system> as an argument
and 'jasmine' (for :env, since it's hardcoded to 'jasmine' in
django_for_jasmine()).

The LMS/CMS server startup depends on the :assets task, which needs
to receive :system and :env arguments. Since the existing server
startup tasks didn't take a :system argument, a new command called
:runserver is created that does take :system, :env, and :options
arguments. The old server startup tasks are adjusted to wrap the one
:runserver task that does all of the heavy lifting.

Rather than directly invoke command-line Python (and Mako) from the
assets Rakefile, or call an external Python script, use a Django
management command to preprocess all asset template files.

An "asset template file" is defined as a static asset file with a
file extension indicating that it needs to be run through a template
engine prior to Sass/CoffeeScript compilation or packaging with other
assets. The preprocess_assets management command will look through
all of the files listed in the `STATICFILES_DIRS`, preprocessing each
as needed. Preprocessing strips off the special template file
extension, creating a new file in the process.

Currently, the only variable accessible in an asset template file is
the `THEME_NAME`, defined in the settings.

Add partial credit for foldit