This allows "invoke" to be called within sub directories of a project.
Note to self: #92 probably duplicates this.
The ``Loader`` should seek towards the file system to find a collection
#131 also semi related to this (though not exactly.)
In addition, I just pushed 625cb8e and e3ba34b which fix a commonish problem re: third party tasks.py modules masking "local" ones.
However, that's also only somewhat related - I'm not sure I understood what this ticket meant before but now I do, the scenario described is:
The reason I didn't really "get" this before is my typical scenario is to "skip" step 2 above - all my tasks.py are in Python projects installed to Python's path via pip install -e or python setup.py develop. When this is done, that tasks.py is now discoverable via sys.path and is then loaded by Invoke no matter where your CWD happens to be.
pip install -e
python setup.py develop
I'll try to actually review this PR (and compare it to #92) soon.
Changelog, closes #92, closes #87
This should work as of the next feature release (or master :)). For more discussion see the latest comments on #92. Thanks!