Re: Isolating Django Models

rozwell @ IRC helped me out substantially by showing me these two links: http://www.b-list.org/weblog/2007/sep/22/standalone-django-scripts/ http://code.djangoproject.com/wiki/IrcFAQ#Shell Blaine On Thu, Jun 25, 2009 at 11:23 AM, Blaine Booher wrote: > Hey everyone, > I was wonderi

Changing the 'ipython' path executed with manage.py shell

Hey everyone, I love using ipython and pylab to plot data. I have to run it like this: 'ipython -pylab' to get the pylab stuff imported correctly into ipython. I notice that "python manage.py shell" spits me out into ipython. Where would I add the '-pylab' option so that it spits me out into

Isolating Django Models

Hey everyone, I was wondering the best way to isolate django models so they can be used in other python applications. I have seen the django extensions, which are very helpful. But a 'job' is still coupled to the django environment. Ideally I'd like to do this: * Write some function foo() that

Re: Scientific Data Frontend with Django

: > > If you have a lot of data pytables may be an option (see link below). > It can store data as numpy arrays directly rather than having to > convert to such an array after reading from an sql database. > > http://www.pytables.org > > Vincent > > > > On Jun 18, 1:15

Re: Scientific Data Frontend with Django

Thank you Rajesh, Vincent, Nick, and Hernan for the helpful suggestions. This is definitely a route I am going to explore. I'll post some updates to the list if anything comes out of it. Would you recommend importing the data into django models and tables, or keeping the db separate and independe