On Thu, 2009-02-12 at 02:14 -0800, Waldemar Kornewald wrote:
> On 12 Feb., 03:51, Malcolm Tredinnick
> wrote:
> > > Is the plan somewhere on the wiki?
> >
> > No, because it's only something I'm pulling together slowly in my head.
>
> I hope you've read my wiki page, so that in the end Django is
On Fri, 2009-02-13 at 04:57 -0800, zvoase wrote:
> Hi all,
> Recently I wrote a blog post (http://bit.ly/HM3hC) on my project
> conventions; it began by talking about how I like to maintain
> different settings 'modes' for debugging, staging and production, and
> the ways in which I do this. I
There was recently a patch to http://code.djangoproject.com/wiki/ProfilingDjango
that adds a --profile argument to "manage.py runserver" to allow
profiling on the development webserver (great for testing).
Are there any thoughts to pull this into trunk?
--~--~-~--~~~--
Hi Zack --
The standard way of doing this is with multiple settings files,
leaving it up to the application server (e.g. mod_wsgi) to switch
between them (i.e. dev boxes load ``dev_settings.py``; prod loads
``prod_settings``.)
Reading your email I can't tell if you'd just like to have this
docum
On Feb 12, 10:35 pm, rpst...@gmail.com wrote:
> Greetings Django Developers,
>
> Allow me to introduce myself; my name is Rory Tulk. I'm a grad
> student at the University of Toronto. A small team of students and I
> are investigating possible implications of unifying the process of
> specifying
Hi all,
Recently I wrote a blog post (http://bit.ly/HM3hC) on my project
conventions; it began by talking about how I like to maintain
different settings 'modes' for debugging, staging and production, and
the ways in which I do this. I've had quite a few responses from
Djangonauts on how they
