Hi Alex, On 04/12/2012 01:07 PM, Alex Ogier wrote: > 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?
Sorry, I wasn't clear - I already know what the immediate cause of the problem is, and it's easy to reproduce manually. "startproject" takes the actual files in django/conf/project_template/ as the template for the new project. If an installation of Django 1.4 is installed over top of an installation of Django 1.3 (and I mean literally on top of, in the same filesystem tree), then the project template files that were moved to a subdirectory in 1.4 (__init__.py, urls.py, settings.py) are found in both locations. So even if it's purely the 1.4 startproject code running, it'll install these extra files, because it finds them there in the project template. The open question is just how this situation occurs in the first place. In other words, which particular buggy installer or installation technique is causing an overlaid installation like that, so we can warn people away from it and better advise them how to fix it. Carl
signature.asc
Description: OpenPGP digital signature
