Folder depth is wrong? about django-twoscoops-project HOT 8 CLOSED

So are we good? Should I close this ticket?

from django-twoscoops-project.

The first project_name shouldn't have an __init__.py and be on your PYTHON_PATH. That way icecream.urls and icecream.settings.local are both valid.

from django-twoscoops-project.

Hi, sorry if I am a bit confused.

According to the base.py config file. DJANGO_ROOT points to the Configuration Root (name according to the book).

DJANGO_ROOT = dirname(dirname(abspath(__file__)))

__file__ is base.py and after 2 dirname calls it moves to the folder that contains urls.py and settings folder and not the one that contains static and template forlders.

I think there is a confusion between what the book calls DJANGO ROOT PROJECT and DJANGO_ROOT.

Am i wrong?

from django-twoscoops-project.

We'll be clarifying this in a future update or possibly the next full edition.

from django-twoscoops-project.

Just purchased the 1.6 book and looking at the template here, the structure still seems off (or I could be off given my experience is with .NET and Rails).

Anyhow, in base.py I see this:

DJANGO_ROOT = dirname(dirname(abspath(file)))
SITE_ROOT = dirname(DJANGO_ROOT)

Given the definitions provided in the book, these constant should be switched around, no?

Also, I'd recommend changing the name of the lowest "project_name" to something more meaningful like "config." Not only would that simplify what folks are are referring too with they talk about the "project_name" directory, but I think it accurately tells us what is in that folder.

Lastly, the 1.6 book recommends using "unipath" which is not being used here ... the question being, is that still the recommendation or do we go with what is on github?

Thanks - wg

from django-twoscoops-project.

So, after reading the book (1.6 edition), I also came around this issue.
Creating a project called "two" this is what I get for DJANGO_ROOT:

/home/arruda/projects/two/two/two

and SITE_ROOT:

/home/arruda/projects/two/two/

As you see, I think the problem is in DJANGO_ROOT, that's because the following line is wrong:

DJANGO_ROOT = dirname(dirname(abspath(__file__)))

This would work ok if using a settings.py since would get the django root ( and not the project's app).

Then to fix I believe this should work:

DJANGO_ROOT = dirname(dirname(dirname(abspath(__file__))))

from django-twoscoops-project.

Oh, I see now, @manubellido is right, the problem is the name used... it's very confusing...

from django-twoscoops-project.

Lastly, the 1.6 book recommends using "unipath" which is not being used here ... the question being, is that still the recommendation or do we go with what is on github?

I'm wondering the same thing as @wgpubs, has this been answered elsewhere?

Never mind, see #98 (comment).

from django-twoscoops-project.