First stab at converting to invoke tasks

[patcon]

Ref: #2294

[chadwhitacre]

We should vendorize until we don't. No?

[patcon]

haha I guess I was being sneaky :) I'll bundle the tarball.

And bah. I just realized that scrubbing the tarballs out of the git history later is going to break any flavoured markdown links to commit hashes. I was thinking we'd be able to do that with minimal consequence down the road, but it would be an inconvenience to break those :/

[chadwhitacre]

Is the name of the tasks module an invoke magical name?

[patcon]

Yep, tasks is what the file or dir needs to be called, as far as I can tell. You have another preference? tasks is common across rake-like task runners, so non-python folks should recognize it

[patcon]

Look ok? Just want to know whether we like invoke. Feel free to merge, and conversion of the rest can be a new PR (might work on bitcoin payout script first)

[patcon]

Accompanying docs in other PR

[chadwhitacre]

Once you're in a virtualenv, env/bin is on your PATH. So you can just call:

[gittip] $ invoke set_paypal_email ...

[patcon]

Oh. hm. When I run make env, I don't seem to get an active virtualenv... Am I missing something?

[chadwhitacre]

You have to activate the virtualenv yourself, like so:

$ source env/bin/activate

Or you can use bash's . alias for source:

$ . env/bin/activate

I have a shell alias so I can just do:

$ a

[chadwhitacre]

Thanks @patcon! :-)