Python 2.6.5 fixes dozens of issues in the core, built-in modules, libraries,
and documentation since Python 2.6.4 was released back in October 2009. We
highly recommend that you upgrade to Python 2.6.5.
Please see the NEWS file for all the gory details.
http://www.python.org/download/releases/2.6.5/NEWS.txt
Source tarballs and the Windows installers can be downloaded from the Python
2.6.5 page. The Mac OS X disk image will be uploaded soon.
http://www.python.org/download/releases/2.6.5/
For more information on Python 2.6 in general, please see
http://docs.python.org/whatsnew/2.6.html
Please report bugs for any Python version in the Python tracker.
Enjoy,
-Barry
Barry Warsaw
ba...@python.org
Python 2.6 Release Manager
(on behalf of the entire python-dev team)
I've built and used python 2.6.5 on linux without any apparent problems, but the
Windows x86 binary installer stops after compiling a few python source files.
I've tried the Windows x86 installer on two differently configured Windows XP
PCs (SP3 with patches), but I get the following errors during the advanced
compiling of python source files:
"There is a problem with this Windows Installer package. A program run as part
of the setup did not finish as expected. Contact your support personnel or
package vendor."
"Python 2.6.5 Installer ended prematurely ..."
The md5sum of the Windows x86 installer matched the published value. I did not
try not using the advanced option. I reinstalled python 2.6.4 on both of the
PCs without any problems and used the advanced compile option.
Is anyone else having trouble with the 2.6.5 Windows x86 installer?
Peter
Not me. Run
msiexec /i py...msi /l*v py.log
and inspect py.log for errors (post it to bugs.python.org if you can't
determine the cause of the problems).
Are you using SUBST by any chance?
Regards,
Martin
>> Is anyone else having trouble with the 2.6.5 Windows x86 installer?
>
> Not me. Run
>
> msiexec /i py...msi /l*v py.log
>
> and inspect py.log for errors (post it to bugs.python.org if you can't
> determine the cause of the problems).
Martin,
Thanks for the tip about the msiexec command line usage. If I run the
installer without selecting the Advanced compiling option, it works fine.
The relevent part of the log when it fails using the Advanced compiling
option is as follows:
--------------------
MSI (s) (4C:B4) [14:41:27:205]: Doing action: CompilePyc
Action 14:41:27: CompilePyc.
Action start 14:41:27: CompilePyc.
MSI (s) (4C:B4) [14:45:45:528]: Note: 1: 1722 2: CompilePyc 3: C:\bin
\Python26\python.exe 4: -Wi "C:\bin\Python26\Lib\compileall.py" -f -x
bad_coding|badsyntax|site-packages|py3_ "C:\bin\Python26\Lib"
MSI (s) (4C:B4) [14:45:45:528]: Note: 1: 2262 2: Error 3: -2147287038
Error 1722. There is a problem with this Windows Installer package. A
program run as part of the setup did not finish as expected. Contact your
support personnel or package vendor. Action CompilePyc, location: C:\bin
\Python26\python.exe, command: -Wi "C:\bin\Python26\Lib\compileall.py" -f
-x bad_coding|badsyntax|site-packages|py3_ "C:\bin\Python26\Lib"
MSI (s) (4C:B4) [14:47:41:133]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (4C:B4) [14:47:41:133]: Product: Python 2.6.5 -- Error 1722.
There is a problem with this Windows Installer package. A program run as
part of the setup did not finish as expected. Contact your support
personnel or package vendor. Action CompilePyc, location: C:\bin\Python26
\python.exe, command: -Wi "C:\bin\Python26\Lib\compileall.py" -f -x
bad_coding|badsyntax|site-packages|py3_ "C:\bin\Python26\Lib"
Action ended 14:47:41: CompilePyc. Return value 3.
Action ended 14:47:41: INSTALL. Return value 3.
--------------------
I believe the cause of the installation failure message is with the
syntax of the following command:
C:\bin\Python26\python.exe -Wi "C:\bin\Python26\Lib\compileall.py" -f -x
bad_coding|badsyntax|site-packages|py3_ "C:\bin\Python26\Lib"
If you run this command in the Windows XP shell, it yields an error. If
you wrap the -x option's args in double quotes, it runs ok (except for a
syntax error when compiling one of the python source files - I don't
remember which one):
C:\bin\Python26\python.exe -Wi "C:\bin\Python26\Lib\compileall.py" -f -x
"bad_coding|badsyntax|site-packages|py3_" "C:\bin\Python26\Lib"
So it appears that the Windows XP shell is interpreting the "|"
characters within the -x option's args as pipe characters and trys to
pipe the "multiple commands" together. The simple work around is to not
use the Advanced compiling option.
Peter