I missed the previous discussion, but I'm not pleased with this change. The developer version of Django is made available only via Subversion, so the requirement for internet access at install is hardly a disadvantage. Django is, after all, a web framework!
The best way to install development Django on a Windows system has been to use the setuptools-provided command: setup.py develop With setuptools, this command copies nothing to site-packages except a setuptools-based link to the Django checkout, and Django is easily kept up to date with svn up. SInce Windows has no built-in linking, this setuptools-based linking is quite useful, and especially for newbies! This same installation approach has in my experience worked worked equally well on linux. (That this approach has not been mentioned at the front of the tutorial is an issue with the tutorial, not with setuptools. I first discovered it in the comments section for tutorial 1.) On Oct 16, 5:03 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote: > Hi all, > > I've refactored Django's setup.py so that it uses the plain Python > distutils installation method rather than ez_setup/setuptools. This > means it no longer requires an Internet connection to install Django. > Hooray! > > But I have only tested this on Linux, so I'd appreciate it if folks > could test out the command "python setup.py install" on various > different platforms. Just grab the SVN version of Django and try > installing it using "python setup.py install". > > For the record, we previously discussed this on django-developers here: > > http://groups.google.com/group/django-developers/browse_thread/thread... > > The "straw that broke the camel's back," in this case, happened this > weekend when I was doing a Django tutorial in Boston and encountered > two people who'd had problems installing Django due to a setuptools > problem that was out of our control. (Namely, it was due to the fact > that Python 2.5's version of setuptools required a certain version of > ez_setup, or vice versa, or some other peculiar problem like that, > which was out of our control.) > > There was something about seeing this problems in real life, with > face-to-face conversations with real Django users, that finally put me > over the edge. > > Adrian > > -- > Adrian Holovaty > holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
