Forwarding part of a reply that I felt had use for the list at large...
On Sun, Feb 26, 2012 at 11:04 PM, Chris Withers <address@hidden> wrote:
> [...] No 3 yet, but as
> more of the libraries I use get there (Pyramid, SQLAlchemy, psycopg2,
> mysqldb) I'll be looking to add 3.x and drop 2.5.
Should mention here that assuming things look good for us moving to
Python 2.6, having Python 3.x compatibility will be a higher priority
for us going forwards. Hopefully via the "one codebase that runs on
both w/o needing 2to3" approach.
> Tasks that (could be) executed locally would be awesome. Is there any
> support for that currently?
Depends what you mean, but local-only tasks (read: a task that
contains no run/sudo/put/get/etc calls, just Python or local()) have
been supported literally forever :)
If you meant "tasks written with run/sudo which can be automagically
executed against a (non ssh-bearing) localhost instead", that's
oft-requested but not in yet (though the move to Invoke will bring us
closer to it being a reality.)
I wrote something to handle this in the djeploy library (which I believe is still part of #461)
It's a Command class that executes based on whether or not the "deploy" is local or not.
See the Command class here:
In order for it to be set to run locally, you have to set the "run_type" variable to "local"
Example here:
Hope this helps.
Peter