win32all-129-update.exe - Is it needed?

Mark Hammond mhammond at skippinet.com.au
Mon May 8 00:49:41 CEST 2000


I will update the web page to hopefully clear up some of this confusion:

* win32all-129 was released to registered users quite some time ago
(registered users now have build 132 (for 1.5.2) available

* There were bugs, and instead of releasing a complete new build, I
released the update.  It only changes files installed by 129.

* Therefore, you should install win32all-129, then win32all-129-update.

* If you have any earlier builds (eg, 128) already installed, the
installation of 129 will suggest and offer to uninstall the previous
versions.

Mark.

"Joe Smith" <JoeSmith at bogusaddress.com> wrote in message
news:YhjR4.44823$k5.1318845 at news1.frmt1.sfba.home.com...
>
> This was supposed to be installed before I install 129?
>
> <aklietz at my-deja.com> wrote in message
news:8f30cp$g5m$1 at nnrp1.deja.com...
> > Good question!  With 663K of patches presumably to the core Python
> > 1.5.2 distribution, I would hesitate to install win32all129 without
it.
> >
> > Version 128 mentioned only a single patch as far as I know
(pyclbr.py).
> >
> > The download site is
> > http://starship.python.net/crew/mhammond/win32/Downloads.html
> >
> > -Alan
> >
> > In article <X73R4.44404$k5.1290605 at news1.frmt1.sfba.home.com>,
> >   "Joe Smith" <JoeSmith at bogusaddress.com> wrote:
> > > On the starship site is says:
> > >     Also download and install the patch set for build 129 -
> > > win32all-129-update.exe (663,799 bytes)
> > >
> > > Is this needed if one installs win32all-129.exe?
>
>
>





More information about the Python-list mailing list