Weird bug - directory with reitveld installation can not be named "codereview"

[anatoly techtonik]

Hi,

I've just wasted some hours on a very weird bug, but don't know where
to report it - to Django or here.
When rietveld example is installed in directory named
"codereview" (e.g. /home/user/codereview), the ./manage.py script
fails with the message:

Error: Could not import settings 'codereview.settings' (Is it on
sys.path? Does it have syntax errors?): No module named settings

If the directory is renamed to anything else (/var/rietveld of /home/
user/rietveld), everything goes fine. Environment is clean, files are
from a fresh checkout. The directory structure is below.

.
|-- codereview/
|-- django/
|-- gae2django/
|-- patches/
|-- rietveld_helper/
|-- static/
|-- templates/
|-- Makefile
|-- README
|-- TODO
|-- UPDATES
|-- __init__.py
|-- __init__.pyc
|-- dev.db
|-- manage.py*
|-- settings.py
|-- settings.pyc
`-- upload.py*


Is it a Django bug?
--
anatoly t.

[Ilia Mirkin]

No insight as to what the problem is, but try running with python -v
-- that will print all if python's import decisions, and may shed
light unto the situation.

--
Ilia Mirkin
imi...@alum.mit.edu

[Andi Albrecht]

I've seen this behavior before. It happens if the directory that contains manage.py has the same name as an application in this directory (aka Django project) *and* if there's an __init__.py. Django's import mechanism get's confused then when it tries to import "codereview".

The Django tutorial has a short note about avoiding built-in module names (http://docs.djangoproject.com/en/dev/intro/tutorial01/).

Andi

[anatoly techtonik]

I see Stani reported the same issue -
http://code.djangoproject.com/ticket/5217 but seems like it was marked
as duplicate of a wrong ticket. The root of the problem is in
http://code.djangoproject.com/ticket/1908

Seems like this ticket should be revisited. I've wasted a lot of time
and somebody else will.
--
anatoly t.

[Andi Albrecht]

On Tue, Dec 7, 2010 at 8:00 PM, anatoly techtonik <tech...@gmail.com> wrote:

I see Stani reported the same issue -
http://code.djangoproject.com/ticket/5217 but seems like it was marked
as duplicate of a wrong ticket. The root of the problem is in
http://code.djangoproject.com/ticket/1908

Thanks for pointing to this ticket! It's really a annoying issues where one can really waste a lot of time.