envy reset feature

This release introduces envy reset. This is useful for dropping stale backups of older package versions without re-applying the changes to the live site-package in your virtualenv.

To drop a backup for a specific package, say, bar, run:

(foo)$ envy reset bar
dropping saved envie for bar

To remove all backups for a given environment, call it foo, run:

(foo)$ envy reset --all
dropping saved envie for bar
dropping saved envie for baz
dropping saved envie for requests

add envy diff

This release implements a new feature, envy diff, which allows the user to see a diff between the backed up (clean) copy of a package, and the current copy living in site-packages.

envy clean --all added

This release introduces a new feature allowing users to clean all envy edit's or sync's at once, as opposed to individually.

For example, assume that a user has made edits to both foo and bar in some virtualenv, call it env. Previously, in order to return the foo and bar site-packages to their original state, the user would need to run both
envy clean foo and envy clean bar.

Now, the user can accomplish this in one step by running envy clean --all.

Fix missing test depdency

explicitly require 'mock' in tests_require in setup.py

Support deeply nested files

This release closes #5 ( envy can now work with deeply nested files)

IE: $ envy edit somepackage/somepackagei/deep/nest/somemodule.py will now work correctly

thank you @andrewgross for finding and fixing this issue!

envy v0.0.8

This release addresses the vim problems discussed in #4.

If vim is set as $EDITOR, envy will use the standard default editor (vi) instead.

For thoughts on a better workaround for #4, (or a solution), please share on the issue thread.

v0.0.7

Only a few small changes here (although I've forgotten to tag some recent releases)

-- Prompt to the user when they use envy on a virtualenv that has already been backed up. This is important because if a user updates a version of a library (after having forgotten to run envy clean), and then uses envy again and this time remembers to run envy clean, they can end up with a stale version in their virtualenv.

Small patch, removed some unneeded code that was being used

v0.0.4

bump to 0.0.4 :balloon: