[IPython-user] win32 installer woes...

Fernando Perez Fernando.Perez at colorado.edu
Tue Jan 25 11:38:53 CST 2005


Fernando Perez wrote:
> Fernando Perez wrote:
> 
>>Hi all,
>>
>>after Viktor's excellent win32 installer work, we have something which 
>>_almost_ works.  Except I have a really nasty problem.  I have just posted a 
>>message to c.l.py  asking for help, which I repost here in case anyone can 
>>help or has a good solution.

Final followup in case anyone is interested.  T. Heller just replied to my 
c.l.py query with this.

Cheers,

f

###########################################################
Re: Installer made with bdist_wininst segfaulting...
From: Thomas Heller <theller at python.net>
Date: Tuesday 25 January 2005 08:02:56 am
Groups: gmane.comp.python.general
References: 1

Fernando Perez <fperez.net at gmail.com> writes:

 > Hi all,
 >
 > I am seeking advice/help from those with more win32 experience than myself.  I
 > am trying to build a proper win32 installer for IPython, after a user did most
 > of the hard work.  For the most part, it's working very well, but I am running
 > into a nasty problem, which took me a few hours to finally understand.  This
 > smells to me like a python  bug, but I could be wrong.  Much googling didn't
 > turn up anything relevant.
 >
 > Here is a brief summary: if the installer file is run from a windows drive 
which
 > is different from the one where python resides (and hence where ipython will
 > end up), the installer segfaults.  No traceback, nothing, just a segfault
 > (well, one of those Windows dialogs asking me to send a binary traceback to
 > Redmond, but not a proper Python traceback).

There are a couple of known bugs in bdist_wininst, and you just reported
another one.  All these bugs are related to using the
post_install_script, and show up when either (thats what I currently
remember):

- the installer is run from a readonly location,
- the installer is run from a different drive (as you reported)
- the installer installs for Python 2.4

I will fix these issues in Python 2.3.5, which will probably be out as a
release candidate this week, and in Python 2.4.1.

I urge everyone to install this release candidate, rebuild the
installer with it, and test them thoroughly.

Thanks,

Thomas




More information about the IPython-user mailing list