On Tue, Oct 27, 2009 at 4:06 PM, Kevin Teague wrote:
> Structure a Django project so it has the same layout as a normal
> Python project. Which might look something like:
>
>myinstance/
>setup.py
>settings.py
>bin/
>manage.py
>mysite/
On Oct 26, 7:23 pm, Tobias McNulty wrote:
>
> IMHO the project namespace is a useful one to keep around. If you lose the
> project name space, then you risk polluting your python path with a lot of
> generic 'urls' modules, among other things.
>
> If your directory
> To fix the code is easy enough. But to update all of the relevant
> documentation and to require all existing Django deployments to have
> to migrate their project structures (or change all of their imports)
> to upgrade is a much bigger issue to tackle.
Thank you for answer.
Do you think it's
> IMHO the project namespace is a useful one to keep around. If you
> lose the project name space, then you risk polluting your python path
> with a lot of generic 'urls' modules, among other things.
I don't understand why in tutorial all imports contain project name.
I think this is wrong
On Mon, Oct 26, 2009 at 8:23 PM, Kevin Teague wrote:
>
> It's Python which doesn't allow dots in the name of a package,
> although it's Django which is putting the name of your project name on
> sys.path. This was intentional, see the django.core.management
> package:
>
>#
Hello, django developers!
On my server every project has it's own folder which name is the same
as project hostname(ex. /home/testsite.com). Bug django don't allow
dots in "project name".
I think we can fix it. For example by avoiding starting import with
project name.