Re: virtualenv and standalone scripts

I have my .bashrc set to source the virtualenv, and I source .bashrc in any shell scripts that need to run via cron. That works out well for me, and was even seamless when I upgraded our server to Python 2.7 last weekend -- I didn't have to change a thing in any script, and just one line in .bashrc

Re: virtualenv and standalone scripts

On 24 August 2010 06:54, Oivvio Polite wrote: > Following advice on this list I've moved to virtualenv+pip to manage my > django stack, which so far is working out nicely. > > But what should I do about standalone scripts? Say I have a project > called mysite. If I'm in a virtualenv and execute a

Re: virtualenv and standalone scripts

On Aug 23, 1:54 pm, Oivvio Polite wrote: > Following advice on this list I've moved to virtualenv+pip to manage my > django stack, which so far is working out nicely. > > But what should I do about standalone scripts? Say I have a project You need to load up the current project environment at the

Re: virtualenv and standalone scripts

And what about using "console_scripts" entry in your setup.py script ? http://www.google.com/search?q=console_scripts On Mon, Aug 23, 2010 at 11:11 PM, Oivvio Polite wrote: > On Mon, Aug 23, 2010 at 10:54:21PM +0200, Oivvio Polite wrote: > > > >

Re: virtualenv and standalone scripts

On Mon, Aug 23, 2010 at 10:54:21PM +0200, Oivvio Polite wrote: > > What's the right way to go about it? > Ok, just did some more googling and found out about custom management commands, that clearly are the django way of solving my problem. oivvio -- http://pipedreams.polite.se/about/ --

virtualenv and standalone scripts

Following advice on this list I've moved to virtualenv+pip to manage my django stack, which so far is working out nicely. But what should I do about standalone scripts? Say I have a project called mysite. If I'm in a virtualenv and execute a standalone script, mysite won't be on my pythonpath and