It's part of the issue #20 (weird path on Windows). Django File class used
a full file path which resulted in path like C:\Example\pinry\static\C:\... which
is obviously invalid.

On Windows using virtualenv/buildout combo is easier than using raw virtualenv/pip, commit
files used by buildout to configure environment.

It is a milestone of sort, from now on we're commited to write
correct two-way migrations for our code. It's one of the last
things to be done before an official v1.0 release.

We have to call lightbox() when new pin is created so its
onClick listener is registered.

TastyPie 0.9.13 doesn't install (reported upstream at
https://github.com/toastdriven/django-tastypie/issues/873) so use
0.9.12 for now.

This commit is a foundation upon a more robust image fetching code
will be built in the future, and it already fixes at least one weird
issue I've seen.

Use forked django-images for now, until we can communicate with the
upstream about it. Fixes #4

show edit buttons only on mouse over (new)

staticfiles_urlpatterns() add only handler for serving /static/ path,
add pattern for /media/.

Finally had time to figure out the problem "caused" by django_compressor,
so we can no re-enable it. Fixes #3

Factory Boy provides us with a better way of populating complicated
fields (like M2M relations) than overriding _prepare class method,
so we should be using them.

There has been issues when running a full test suite (for pinry and
the entire Django stack), and test fixtures are hard to maintain anyway,
so rewrite tests to use a Model mocker library (Factory Boy) to populate
database.