Is there any reason to use either setuptools or distutils if one is doing an automated install of Django? Isn't it just copy or link the django directory to the Python path, copy django-admin.py to an executable path, and you are pretty much done?
How would one now recommend that a new Windows developer install Django in a such a way as to facilitate keeping his Django updated to the trunk? The easiest to explain approach that I know about would be to ignore Django's setup.py. Instead install setuptools, manually create a Django.eggs-link file in site-packages, and then copy django-admin.py to the Python scripts directory. There are other ways - mostly involving access to Windows' painful UI for creating persistent environment variables - but they are not easier to explain or perform than the technique I just described Thus this change seems like a regression in the ease of a best-practices installation for new developers on Windows. And in defense of Phillip Eby's very laudable efforts, I suspect that the vast majority of all issues with the setuptools install would have been resolved by simply changing the instructions to: 1) First download and run the latest ez_setup.py 2 Checkout Django trunk 2) Then run python setup.py develop And users on all platforms would have then had a Django that is easily updated by svn up. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
