That seems like too much to ask. "setup.py install" should Just Work(tm), and if django requires that a certain directory be clean of any .py files in order to function properly then "setup.py install" should make that happen. The note might still be valuable, because we should inform people that untar-ing a version on top of another can cause problems like this, but breaking "setup.py install" shouldn't be necessary.
If none of these are acceptable, then we can always use a different directory (django/conf/project_template_new), so that conflicts don't happen. It's a bit hacky but it would work. Best, Alex Ogier On Thu, Apr 12, 2012 at 5:16 PM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > On 12 avr. 2012, at 21:16, Carl Meyer wrote: > > > 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. > > This problem occurs at least when you run "setup.py install" before and > after the commit that introduced the new project layout. > > Some people who had the habit of running "setup.py install" from a git > clone to keep up-to-date with the development version reported the problem. > (Just to be 100% clear — this technique doesn't work because it doesn't > remove .py or .pyc files that are removed from Django.) > As a result, I added a warning to the docs in r17636. > > Most likely, installing 1.4 with "setup.py install", as explained in our > docs [1], has the same result when 1.3 was previously installed in the same > fashion. > > I suggest we add a warning to this section of the docs: "if a previous > version of Django is installed, go delete it manually in your site-packages > directory" (unless there's a better method to remove a Python package?) > > Best regards, > > -- > Aymeric. > > [1] > https://docs.djangoproject.com/en/dev/topics/install/#installing-an-official-release-manually > > -- > 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. > > -- 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.
