Re: extra files in startproject (was: Django is not a serious framework, really)

[Alex Ogier]

Maybe it would be worth experimenting with various combinations of django
1.x django-admin.py executables with django 1.4 libraries? Maybe if
django-admin.py is a symlink into a 1.3 tree but django 1.4 is on the
search path this stuff could crop up?

Best,
Alex Ogier
On Apr 12, 2012 2:32 PM, "Carl Meyer"  wrote:

> Hi Jason,
>
> On 04/11/2012 06:10 AM, Jason Ma wrote:
> > Hi,
> > I download and tried to use the Django 1.4 yesterday. I am a dummy
> > and I just follow the official document, but When I just start a
> > project.
> > I found that it is what I see from my computer:
> >
> > jason@jason-pc:~/workspace/hunqing$ tree .
> > .
> > ├── hunqing
> > │   ├── __init__.py
> > │   ├── __init__.pyc
> > │   ├── settings.py
> > │   ├── settings.pyc
> > │   ├── urls.py
> > │   ├── urls.pyc
> > │   ├── wsgi.py
> > │   └── wsgi.pyc
> > ├── __init__.py
> > ├── manage.py
> > ├── settings.py
> > └── urls.py
> >
> > but what doc say?
> > mysite/
> > manage.py
> > mysite/
> > __init__.py
> > settings.py
> > urls.py
> > wsgi.py
>
> Others have commented on the pyc files, but I don't think that's really
> the point here. The point is that there is an extra __init__.py,
> settings.py, and urls.py in the outer directory next to manage.py that
> should not be there.
>
> This is definitely a bug, and it's one that I've already seen reported
> several times, but it is not a bug in Django. With a clean installation
> of Django 1.4, the tutorial steps work as advertised. This bug occurs if
> somehow your installation of Django 1.4 is "layered" on top of an
> installation of Django 1.3, without the 1.3 installation ever having
> been removed. I'm not sure how this happens, but my best guess is that
> it could happen if you are using a very old version of pip (like, pip
> 0.3 era, before pip gained uninstall support). You're most likely to be
> using an old pip if you are using a Linux distribution's packaged pip;
> those tend to be quite outdated.
>
> If you are interested in helping to solve this issue (as opposed to, for
> instance, trollish hyperbole), it would be very helpful to know what
> operating system and version you are using, and how you installed Django
> 1.4 (i.e the exact commands you used).
>
> Thanks!
>
> Carl
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: extra files in startproject (was: Django is not a serious framework, really)

[Carl Meyer]

Hi Jason,

On 04/11/2012 06:10 AM, Jason Ma wrote:
> Hi,
> I download and tried to use the Django 1.4 yesterday. I am a dummy
> and I just follow the official document, but When I just start a
> project.
> I found that it is what I see from my computer:
> 
> jason@jason-pc:~/workspace/hunqing$ tree .
> .
> ├── hunqing
> │   ├── __init__.py
> │   ├── __init__.pyc
> │   ├── settings.py
> │   ├── settings.pyc
> │   ├── urls.py
> │   ├── urls.pyc
> │   ├── wsgi.py
> │   └── wsgi.pyc
> ├── __init__.py
> ├── manage.py
> ├── settings.py
> └── urls.py
> 
> but what doc say?
> mysite/
> manage.py
> mysite/
> __init__.py
> settings.py
> urls.py
> wsgi.py

Others have commented on the pyc files, but I don't think that's really
the point here. The point is that there is an extra __init__.py,
settings.py, and urls.py in the outer directory next to manage.py that
should not be there.

This is definitely a bug, and it's one that I've already seen reported
several times, but it is not a bug in Django. With a clean installation
of Django 1.4, the tutorial steps work as advertised. This bug occurs if
somehow your installation of Django 1.4 is "layered" on top of an
installation of Django 1.3, without the 1.3 installation ever having
been removed. I'm not sure how this happens, but my best guess is that
it could happen if you are using a very old version of pip (like, pip
0.3 era, before pip gained uninstall support). You're most likely to be
using an old pip if you are using a Linux distribution's packaged pip;
those tend to be quite outdated.

If you are interested in helping to solve this issue (as opposed to, for
instance, trollish hyperbole), it would be very helpful to know what
operating system and version you are using, and how you installed Django
1.4 (i.e the exact commands you used).

Thanks!

Carl



signature.asc
Description: OpenPGP digital signature