On 7/22/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
> In http://code.djangoproject.com/wiki/VersionOneFeatures I see Windows
> Installers listed with no leader and no start status. I'm pretty
> comfortable building installers using NSIS (nsis.sf.net) as we do that
> where I work and could chip in here.
Don't you think that using standard distutils is enough? You just type
python setup.py bdist --format=wininst
And voila - windows installation has been created.
> * Install Python? Full version or other? v2.4?
Why do you like old versions? Do you install Python in Debian from
packages? No. Do you have problems with third-party packages? No. Why
do you think that 2.4 is better than 2.5? I understand why authors of
Django are trying to kepp compatibility with old versions, but this...
> * Uninstaller?
Packages that are bundled using distutils always have standard uninstaller.
> If I were to do this by default, I'd probably approach it as follows:
> * Bundle Python v2.4 but incorporate checks for pre-existing Python,
> or maybe just execute the pre-existing Python installer. (Testing
> needed.)
> * Use SQLite.
> * No common libs, just bare minimum to get Django running.
As Django user I would be dissatisfied if Django's installation will
ask me about all these useless things - why it cannot install so
simple as other Python extensions and packages do?
--
=^ ^= Vsevolod S. Solovyov aka Murkt
( ) vsevolod.solovyov [at] gmail.com
~ [Team ·Їжачки - сумні падлюки], [Майстер Хача-Пачі]
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
