Martin v. Löwis wrote:
Looking at http://www.python.org/dev/buildbot/, we are still missing buildbots
for the release26-maint and release30-maint branches. Is someone working on
that?
Yes. I won't enable 2.6 build slaves until 2.5.3 is released, but will
afterwards.
How does one actually dow
I went to upgrade a Vista machine from 2.6.1 to 2.6.2 and got error 2755
with the message "system cannot open the device or file".
I uninstalled 2.6.1, removing all residual files also, and got the error
message again.
When I ran msiexec as follows to get a log, it magically worked:
msiexec
Martin v. Löwis wrote:
>> Thanks for fixing these Martin!
>
> I have now also uploaded signed MSI files for 3.0a3.
>
> I have not tested them on a machine which doesn't have the
> VS 2008 CRT installed (as all the machines I can access
> right now do have it); please report what works and what
>
Jim Kleckner wrote:
> Martin v. Löwis wrote:
>>> Thanks for fixing these Martin!
>> I have now also uploaded signed MSI files for 3.0a3.
>>
>> I have not tested them on a machine which doesn't have the
>> VS 2008 CRT installed (as all the machines I ca
Martin v. Löwis wrote:
>> When I install 2.6a1 onto a Windoze machine without any previous
>> install, I get a dialog:
>> 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 ven
Martin v. Löwis wrote:
> Please compress it, and make a bug report on
> bugs.python.org.
Submitted as:
http://bugs.python.org/issue2256
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
Martin v. Löwis wrote:
>> That's odd. In theory, having msvcr90.dll in C:\Python26 should be
>> sufficient, as once python.exe is loaded, its directory is added to
>> the DLL search path. Maybe it's something to do with the "side by side
>> manifest installation" stuff (or whatever it's called).
>
Barry Warsaw wrote:
...
For more information and downloadable distributions, see the Python
2.6 website:
http://www.python.org/download/releases/2.6/
The .msi for 2.6a3 seems to be missing from:
http://www.python.org/ftp/python/2.6/
and the download link from this page gives a 404:
http:/
In building a package with several platforms, I
ran across the warning message below from Visual
Studio 2008. Should we add the /EHsc option to the
compile_options in distutils for MSVC? Or is it more
complex than that...
This link describes the warning:
http://tinyurl.com/4fmjue
http://msdn.
Martin v. Löwis wrote:
In building a package with several platforms, I
ran across the warning message below from Visual
Studio 2008. Should we add the /EHsc option to the
compile_options in distutils for MSVC? Or is it more
complex than that...
Who is "we"? If you have a module that uses C++
I gave it a try with cygwin-hosted mingw just to see
if that would work as an alternative to VS2008/VC9 to
figure out some linkage problems.
I tried:
python setup.py build_ext --compiler mingw32
and got a version string issue noted below which
rejects the version string printed from the loader
11 matches
Mail list logo
