On 12/8/05, Pedro Furtado <[EMAIL PROTECTED]> wrote:
> > And I think that the DATABASE_ENGINE setting should be set to empty
> > string "" in settings.py by default, so it can detect if it hasn't
> > been properly set up.
>
> +1 here. I presume it will fix this minor bug and this way won't
> privi
> I agree you shouldn't be forced to set up db, but that's not why you
> had your problem - it was because you don't have postgresql driver for
> python installed.
> It tries do call them, fails and prints out an error. Switch it to
> mysql (or whatever you're using) and everything will be honky-d
I agree you shouldn't be forced to set up db, but that's not why you
had your problem - it was because you don't have postgresql driver for
python installed.
It tries do call them, fails and prints out an error. Switch it to
mysql (or whatever you're using) and everything will be honky-dory.
And I
>This is just a hunch - but you don't have PostgreSQL drivers for
>Python installed do you?
>If you're using mysql, just change "DATABASE_ENGINE" to mysql (or
>whatever else you're using) and you should be able to run the server
>(worked for me).
I'll try to explain my point, Petar.
The auto-gen
Hi Pedro,
This is just a hunch - but you don't have PostgreSQL drivers for
Python installed do you?
If you're using mysql, just change "DATABASE_ENGINE" to mysql (or
whatever else you're using) and you should be able to run the server
(worked for me).
This is definetly a bug: Maybe it's better to
OK, I've added that "Welcome to Django" page. It's displayed ifDEBUG=True and the URLconf is empty. The design is another Wilson
Special.Adrian, I tested here but it seems that you need to configure DATABASE_* before try to runserver.-- Pedro
On 12/6/05, Eugene Lazutkin <[EMAIL PROTECTED]> wrote:
> IMHO, DEBUG=True + empty URLconf should be enough to show "Welcome to
> Django" with appropriate explanation why it was shown ("Because you set
> DEBUG=True, and empty URLconf, that's why!"). :-)
OK, I've added that "Welcome to Django" page
"Adrian Holovaty" <[EMAIL PROTECTED]> wrote
in message
news:[EMAIL PROTECTED]
>The question is where that "Welcome to Django" view lives. It
>shouldn't be in the URLconf by default, because that's crufty. (That
>forces people to remember to delete it.) It's probably safe to
>activate it when th
I just checked in a change (revision 1556) that adds the file
"manage.py" to any new project created with "django-admin.py
startproject".
This is a light wrapper around django-admin.py, except that it
automatically makes sure your project is on the PYTHONPATH and
automatically sets DJANGO_SETTING
