latest.

everything from pypi instead of pulling from git repos.

Factory Boy 2.0 have removed the "extracted_key" keyword argument from
post_generation() hook. Until we can update tests to work with 2.0 make
dependency on 1.3.x branch. In turn, the update got stalled by a bug
in Factory Boy (https://github.com/rbarrois/factory_boy/issues/53).

Too lax unique constraints for Thumbnail coped with "on demand" thumbnail
generation may leave database in inconsistent state where two thumbnail for
the same size are saved. We should be able to prevent that from happening
by generating all thumbnails when we save the image. Should fix #24, but
I can't figure out a way to actually test it.

Remove the scroll event handler when lightbox is active, so pins are
not loaded in background breaking the page layout.

It's still not working completely (you can't run tests from it) but it's enough for installing. Fixes #18

Repeat after me "I'll run a full test suite before pushing changes"

We weren't checking if the Pin submitter is the logged user which made it possible
to pass any submitter to the Pin resource create call. Fix it, and make the submitter
optional.

Make sure that we are using binary mode to read binary files like images, this Fixes #20

Change the settings module and add eggs to the bin/django script path

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