[py-dev] towards a 0.8.0 release!

[Paul Moore]

On 4/24/05, Brian Dorsey <briandorsey at gmail.com> wrote:
> I was thinking of Inno Setup: http://www.jrsoftware.org/isinfo.php
> ... that said... if we can get the standard distutils version working,
> that's probably the best? This is a bit new to me as well... I've
> never really distributed python modules for windows, just
> applications. (That said... the module installers I have used which
> also have scripts never seem to just work for me. :)

I'd very strongly recommend sticking with a standard
setup.py/bdist_wininst installer for Windows. It's what nearly every
other package uses.

I just did a quick test of bdist_wininst and it failed to tidy up
properly, I think largely because it couldn't remove the Subversion
directories. I strongly disagree with the idea of including the
Subversion control stuff in the installed copy, in any case. In my
view,  you shouldn't be doing "svn up" in your site-packages tree,
rather you should be doing it in your build tree, then building a new
installer and running it. This keeps the registry of installed
packages up to date. Of course, on Unix where there is no uninstall
facility (if you puse setup.py install, at least) this is less of an
issue, but it is true on Windows.

Is there any chance of changing the decision to include the .svn
directories - on Windows, if not elsewhere?

Other issues with setup.py - it doesn't seem to build C extensions -
greenlets, specifically, but I notice that popen5 (_subprocess.c) is
included as well - is this right? If so, I'd expect it to be excluded
from Python 2.4 and above builds (which is problematic as long as
there are no C extensions included, as in that case the installer is
version-independent).

Sorry, but I'm not able to go much further with this at the moment. I
hope the above comments are of some help in any case.

Paul.