Hi Brian,
I noticed that each install is separate. Anyway I was too quick with the
last post. Deleting files is relatively simple, since distutils already
sets up the necessary table. My concern was that setup.py would have to
read the Components table to find a component to attach the deletes to.
But distutils uses "pygame1" so no lookup is needed. Thanks to your
additions to setup.py, Brian, most of the work was done for me. So
besides color.py, color.pyc, color.pyo, surfarray.pyd and sndarray.pyd
are there any other files to go. If not then I will commit to SVN.
Should I have some time I will look at the "ProductCode" GUID. It would
be nice if it stays constant for Pygame.
Lenard
Brian Fisher wrote:
I don't know all of what it takes to make uninstalling previous
versions, but evidentally there is some property that defaults to off,
that must be set to "true" to get this behavior:
*RemovePreviousVersions*
I think the main complication with it is making sure the "ProductCode"
GUID is the same for old & new installers yet at the same time the
version numbers go up
On Tue, Jun 3, 2008 at 7:39 PM, Lenard Lindstrom <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Not with Python's msilib unless the whole installer were built
from scratch.
Lenard
René Dudfield wrote:
oh, sorry. I meant...
Could we use the msi lib to delete all the old files somehow?
cu,
On Tue, Jun 3, 2008 at 2:20 PM, Lenard Lindstrom
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
Nothing is deleted. color.py is simply ignored by the
Python interpreter.
Lenard
René Dudfield wrote:
cool.
Maybe the new msi changes stuff make it delete all old
files too?
On Tue, Jun 3, 2008 at 12:01 PM, Lenard Lindstrom
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
Well it doesn't appear to matter. Extension
modules take precedence over
pure Python modules of the same name.
Lenard
Lenard Lindstrom wrote:
That was it. I didn't run config.py first. But
this will complicate
things
for upgrading. I doubt the distutils generated
msi installer remove the
old
color.py module.
Lenard
René Dudfield wrote:
hi,
have you included the new color.c in your
Setup ?
On Tue, Jun 3, 2008 at 2:48 AM, Lenard
Lindstrom <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>
wrote:
Pygame is segfaulting on Windows.
Importing Pygame fails:
Python 2.5.2 (r252:60911, Feb 21 2008,
13:11:45) [MSC v.1310 32 bit
(Intel)]
on
win32
Type "help", "copyright", "credits" or
"license" for more information.
import pygame
Fatal Python error: (pygame parachute)
Segmentation Fault
Not very useful. When a Pygame
application is run without a console
the
dialog box locates the fault in
python.exe. Again not much help. I can
only
limit the problem to one of
pixelarray.c, transform.c, image.c,
draw.c,
time.c, surface.c, font.c and
imageext.c. These were all changed since
the
last working version of Pygame I compiled.
