Re: [Python-Dev] Buildbots for 2.6 and 3.0
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 download the resulting .msi for a build? I poked a 2.6 build to try out the fix for issue4566: http://www.python.org/dev/buildbot/2.6/x86%20XP-4%202.6/builds/90 But searching around I don't see where the resulting files are stored. Where are they located? They used to go in here for 2.6 development: http://www.python.org/dev/daily-msi/ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] 2.6.2 Vista installer failure on upgrade from 2.6.1
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 /i python-2.6.2.msi /l*v install.log Should I attempt to explore this further or just be happy? ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] RELEASED Python 2.6a1 and 3.0a3
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 > doesn't. 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 vendor. Note that it didn't have VS2008 or any other new code installed. When running the Python console, running import Tkinter results in an error saying that _tkinter can't be loaded. DLL load failed. The system can't find _tkinter.pyd _tkinter.pyd and tcl84.dll and tk84.dll are in DLLs and appear to have reasonable permissions. I suspect something in the install failed to set something in the registry. Is there any log file of the install to inspect? ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] RELEASED Python 2.6a1 and 3.0a3
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 can access >> right now do have it); please report what works and what >> doesn't. > > 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 vendor. > > Note that it didn't have VS2008 or any other new code installed. > > When running the Python console, running > import Tkinter > > results in an error saying that _tkinter can't be loaded. > DLL load failed. The system can't find _tkinter.pyd > > _tkinter.pyd and tcl84.dll and tk84.dll are in DLLs and > appear to have reasonable permissions. > > I suspect something in the install failed to set something > in the registry. Is there any log file of the install > to inspect? I forgot to mention that this is on a current-patch XP system and that I also tried python-2.6.13944.msi from the buildbot just in case after uninstalling/reinstalling. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] RELEASED Python 2.6a1 and 3.0a3
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 vendor. >> >> Note that it didn't have VS2008 or any other new code installed. >> >> When running the Python console, running > > How did you do that if you can't install the file? It got far enough to have entries in "All Programs/Python 2.6" ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [Python-3000] RELEASED Python 2.6a1 and 3.0a3
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: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Installing Python 2.6 alpha1 on Windows XP
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). > > Yes, with VS 2008, the DLL search path becomes irrelevant (or so it > seems). > >> Martin, can you comment? It looks like the 3.0 installer uses 2 copies >> of msvcr90.dll, where the 2.6 one doesn't. I would have thought that >> only one is necessary, but Gregor's experiments seem to demonstrate >> otherwise. > > I haven't figured it out myself; it's a complete mess, and Microsoft > is heavily wasting our time. > > It seems that you absolutely *must* have the manifest file in each > directory that has a DLL which links with the CRT. Whether or not > separate copies of the DLL are then also necessary, and whether or > not that causes two copies to be loaded into the address space, > I don't know. HELP > > To reproduce the problem, you probably have to test on a machine > which doesn't have the CRT redistributable installed centrally > (neither through VS 2008 installation, nor by running the > standalone CRT installer, nor by having installed any other software > that provides an SxS copy of the CRT). FYI, here is a related bug report on this: http://bugs.python.org/issue2256 If you send me private email, I can test installs on that machine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] RELEASED Python 2.6a3 and 3.0a5
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://www.python.org/download/releases/2.6/ (This 3.0a5 .msi files are also missing) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Visual Studio 2008 compiler option EHsc ?
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.microsoft.com/en-us/library/2axwkyt4.aspx This link describes a patch: http://tinyurl.com/63bqo2 http://projects.scipy.org/pipermail/numpy-discussion/2007-January/025527.html === Warning message: C:\Program Files\Microsoft Visual Studio 9.0\VC\INCLUDE\xstring(2092) : warning C4530: C++ exception handler used, but unwind semantics are not enabled. Specify /EHsc C:\Program Files\Microsoft Visual Studio 9.0\VC\INCLUDE\xstring(2083) : while compiling class template member function 'void std::basic_string<_Elem,_Traits,_Ax>::_Copy(unsigned int,unsigned int)' with [ _Elem=char, _Traits=std::char_traits, _Ax=std::allocator ] C:\Program Files\Microsoft Visual Studio 9.0\VC\INCLUDE\xstring(2221) : see reference to class template instantiation 'std::basic_string<_Elem,_Traits,_Ax>' being compiled with [ _Elem=char, _Traits=std::char_traits, _Ax=std::allocator ] ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Visual Studio 2008 compiler option EHsc ?
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++ exceptions, you should certainly enable compiler support for exceptions, for that module. In my original email, I referred to the patch for distutils at: http://tinyurl.com/63bqo2 Based on that patch, I made the attached patch in distutils to msvc9compiler.py and that made the complaints disappear (and presumably made the exceptions work?). Is there any downside to doing this by default? Or should I parameterize my build_ext for that platform to include that option? Some of the web pages on the topic suggest that this is due to a change in the compiler behavior with VS2008. So this may bite other people as 2.6 rolls out. I am not an expert in structured exception handling and all the nuances so welcome any advice. Thanks - Jim --- msvc9compiler.py.orig 2008-05-16 16:08:01.619640200 -0700 +++ msvc9compiler.py2008-05-15 16:45:47.493969600 -0700 @@ -375,15 +375,15 @@ self.preprocess_options = None if self.__arch == "x86": -self.compile_options = [ '/nologo', '/Ox', '/MD', '/W3', +self.compile_options = [ '/nologo', '/Ox', '/MD', '/W3', '/EHsc', '/DNDEBUG'] -self.compile_options_debug = ['/nologo', '/Od', '/MDd', '/W3', +self.compile_options_debug = ['/nologo', '/Od', '/MDd', '/W3', '/EHsc', '/Z7', '/D_DEBUG'] else: # Win64 -self.compile_options = [ '/nologo', '/Ox', '/MD', '/W3', '/GS-' , +self.compile_options = [ '/nologo', '/Ox', '/MD', '/W3', '/GS-' , '/EHsc', '/DNDEBUG'] -self.compile_options_debug = ['/nologo', '/Od', '/MDd', '/W3', '/GS-', +self.compile_options_debug = ['/nologo', '/Od', '/MDd', '/W3', '/GS-', '/EHsc', '/Z7', '/D_DEBUG'] self.ldflags_shared = ['/DLL', '/nologo', '/INCREMENTAL:NO'] ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Status of mingw and Python 2.6 ?
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
ld as an inappropriate form.
I seem to recall that mingw was expected to work with 2.6.
Is it?
Thanks - Jim
running build_ext
Traceback (most recent call last):
File "finsim/setup.py", line 96, in
package_dir = {'finsim': 'finsim'},
File "c:\Python26\lib\distutils\core.py", line 152, in setup
dist.run_commands()
File "c:\Python26\lib\distutils\dist.py", line 972, in run_commands
self.run_command(cmd)
File "c:\Python26\lib\distutils\dist.py", line 992, in run_command
cmd_obj.run()
File "c:\Python26\lib\distutils\command\build_ext.py", line 309, in run
force=self.force)
File "c:\Python26\lib\distutils\ccompiler.py", line 1175, in new_compiler
return klass (None, dry_run, force)
File "c:\Python26\lib\distutils\cygwinccompiler.py", line 306, in
__init__
CygwinCCompiler.__init__ (self, verbose, dry_run, force)
File "c:\Python26\lib\distutils\cygwinccompiler.py", line 107, in
__init__
get_versions()
File "c:\Python26\lib\distutils\cygwinccompiler.py", line 430, in
get_versions
ld_version = StrictVersion(result.group(1))
File "c:\Python26\lib\distutils\version.py", line 40, in __init__
self.parse(vstring)
File "c:\Python26\lib\distutils\version.py", line 107, in parse
raise ValueError, "invalid version number '%s'" % vstring
ValueError: invalid version number '2.18.50.20080523'
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
