Django Windows Installers
Rob Hudson
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.
Has it been discussed what the installer should install? I'd be happy
to help out but more specifics would be nice. Here are some general
questions, and if answers come in I'll update that Wiki page to add
"Comments about Specific Features" down below.
* Install Python? Full version or other? v2.4?
* Install a database or just SQLite? Options to install others
(mysql, postgresql)?
* Options for other common libs like Markdown or Textile, etc?
* 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.
Cheers!
-Rob
Vsevolod Solovyov
> 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 ·Їжачки - сумні падлюки], [Майстер Хача-Пачі]
Eugene Lazutkin
Hash: SHA1
Presently I maintain the Windows installer. Because of some reasons (the
main one: core devs don't use Windows) it was not included in the
official download page, so I "distribute" it manually. Send me an
e-mail, and I'll mail it back to you.
If you want to improve on it --- you are welcome to do so.
Thanks,
Eugene
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGpCrTY214tZwSfCsRAjsXAKDAvcbb+YUgrDyCvjoG9ij9RySYVACgxBX3
ahqHb6JaKh27nDa3Rh3071U=
=O1XH
-----END PGP SIGNATURE-----
Kevin Menard
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Presently I maintain the Windows installer. Because of some reasons (the
> main one: core devs don't use Windows) it was not included in the
> official download page, so I "distribute" it manually. Send me an
> e-mail, and I'll mail it back to you.
>
> If you want to improve on it --- you are welcome to do so.
I won't be able to dedicate any sort of actual programming time to
this right at the moment. I would like to suggest packaging it up as
an MSI though. As an MSI, it can be pushed through an entire
organization using GPO. This would be great for making sure that all
devs are using the same version of django. It would also help pushing
out "django as a desktop app"-type deployments.
--
Kevin