Re: extra files in startproject

Hi Carl, Looks fine to me, and I think throwing the warning at the end is indeed a good idea. -Original Message- From: Carl Meyer Sent: Friday, April 13, 2012 2:20 PM To: django-developers@googlegroups.com Subject: Re: extra files in startproject -- You received this message

Re: extra files in startproject

On 04/13/2012 08:33 AM, Carl Meyer wrote: > Thanks Daniel. I'm experimenting right now with a patch to setup.py that > would print a loud warning to console if it detects an existing django/ > directory in the target site-packages. I've filed a pull request (https://github.com/django/django/pull/1

Re: extra files in startproject

directly to the > console. > > Thank you for reading my opinion. > > Daniel > *From:* Florian Apolloner > *Sent:* Friday, April 13, 2012 2:15 AM > *To:* django-developers@googlegroups.com > *Subject:* Re: extra files in startproject > > > > On Friday, Apr

Re: extra files in startproject

You sir are Epic! -Original Message- From: Carl Meyer Sent: Friday, April 13, 2012 10:33 AM To: django-developers@googlegroups.com Subject: Re: extra files in startproject -- You received this message because you are subscribed to the Google Groups "Django developers"

Re: extra files in startproject

On 04/13/2012 08:30 AM, Daniel Sokolowski wrote: > People won’t always read all the docs – it’s a fact – so sooner or later > some other new comer will experience this issue complain, gave up and > worse even blog his/hers negative experience. We do want the newbie > experience to be as painless as

Re: extra files in startproject

@googlegroups.com Subject: Re: extra files in startproject On Friday, April 13, 2012 6:49:32 AM UTC+2, Alex Ogier wrote: I have seen setup.py's that use remove_tree as part of a "clean" command to allow someone to run "setup.py clean && setup.py install" to

Re: extra files in startproject

Hi Alex, On 04/12/2012 10:49 PM, Alex Ogier wrote: > The problem is that not everyone uses package managers. A reasonable > way to track django trunk for example is to periodically pull and run > "setup.py install" which is in most cases approximately idempotent. I > have seen setup.py's that use

Re: extra files in startproject

On Apr 13, 2012 3:30 AM, "Luciano Pacheco" wrote: > > This "import django" will work even when django is not installed, because usually "python setup.py " is ran from checkout of django, that contains the valid folder (python package) named "django". So, this "import django" will import relative t

Re: extra files in startproject

On Fri, Apr 13, 2012 at 5:15 PM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > On 12 avr. 2012, at 23:16, Aymeric Augustin wrote: > [...] > So a documentation fix might not be sufficient to eradicate the problem. > Could we add this in a pre-install hook in setup.py? > > try: >

Re: extra files in startproject

On 12 avr. 2012, at 23:16, Aymeric Augustin wrote: > 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

Re: extra files in startproject

On Friday, April 13, 2012 6:49:32 AM UTC+2, Alex Ogier wrote: > > I have seen setup.py's that use remove_tree as part of a "clean" command > to allow someone to run "setup.py clean && setup.py install" to obtain > a pristine distribution idempotently, which I think is a good idea. > No, they shou

Re: extra files in startproject

On Thu, Apr 12, 2012 at 11:56 PM, Ben Finney wrote: > > Alex Ogier writes: > > > That seems like too much to ask. "setup.py install" should Just > > Work(tm), > > In the absence of a proper package management system (as implemented in > operating systems that solved this problem decades ago), you

Re: extra files in startproject

Alex Ogier writes: > That seems like too much to ask. "setup.py install" should Just > Work(tm), In the absence of a proper package management system (as implemented in operating systems that solved this problem decades ago), you can't expect it to Just Work. Parallel installation of multiple ve

Re: extra files in startproject

On Fri, Apr 13, 2012 at 8:30 AM, Carl Meyer wrote: > Hi Alex, > > On 04/12/2012 04:23 PM, Alex Ogier wrote: > > On Apr 12, 2012 6:16 PM, "Carl Meyer" > > wrote: > [...] > I still think the right solution is to encourage (via the documentation) > installation practices

Re: extra files in startproject

Hi Alex, On 04/12/2012 04:23 PM, Alex Ogier wrote: > On Apr 12, 2012 6:16 PM, "Carl Meyer" > wrote: >> The correct solution is to warn people away from using installation >> techniques in ways they were not intended to be used, and that don't >> work correctly. Repeated u

Re: extra files in startproject

On Apr 12, 2012 6:16 PM, "Carl Meyer" wrote: > > The correct solution is to warn people away from using installation > techniques in ways they were not intended to be used, and that don't > work correctly. Repeated use of "setup.py install" without removing the > previously-installed version is in

Re: extra files in startproject

On 04/12/2012 03:27 PM, Alex Ogier wrote: > 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 b

Re: extra files in startproject

On 04/12/2012 03:16 PM, Aymeric Augustin wrote: > 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 develo

Re: extra files in startproject

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 u

Re: extra files in startproject

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 advis

Re: extra files in startproject

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 coul

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

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

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

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$