django-admin startproject myproject still create myproject\settings

[vivian@…]

Dear Django,

I was trying to do the Django tutorial (using the sqlite3 database but I don't think it is important to what follows)

django-admin startproject myproject

And Django complain after:

django-admin init --settings=myproject.settings

After debugging a bit it appears that my settings was'nt read.

In the tutorial you ask for modification into:

myproject/settings.py

But django-admin startproject myproject still create

myproject/settings and
myproject/settings/init.py

So the command "import myproject/settings" import myproject/settings/init.py instead of myproject/settings.py

If I delete myproject/settings think seems to go smoothly.

I know that few weeks ago you merged admin and main sites, I wonder if django-admin startproject has been updated since then.

Thanks very much for your nice project, nice web site and clear documentation it make me wanting to do web sites :-) with Python.
Consider this ticket as the expression of my gratefullness and my awkward whish to contribute.

Vivian.

[Adrian Holovaty]

Thanks for the ticket, Vivian. Can you check to see whether you have a "django/conf/project_template/settings" directory in your Django source-code tree? If you do, you'll need to delete that. We removed that directory a while ago, but Subversion tends to hold onto directories through "svn update".

[anonymous]

Thanks for your reply and sorry for my wrong ticket. My mistake was that I used setup.py install without deleting the build folder and it seems that the setup.py install do not clean it before hand. The django/conf/project_template/settings folder was in that folder and was reinstalled each time I run setup.py install.

Thanks again for your reactivity and your beatifull framework :-)
Vivian.

[Adrian Holovaty]

Cool, no problem. I'm closing the ticket.