[issue7833] Bdist_wininst installers fail to load extensions built with Issue4120 patch

2010-06-01 Thread Koen van de Sande
Koen van de Sande k...@tibed.net added the comment: issue8870 and issue8871 are not related to this one. There, the UAC elevation fails, here the issue is with the MS runtimes, elevation is working fine. -- ___ Python tracker rep...@bugs.python.org

[issue8870] --user-access-control=force produces invalid installer on Vista

2010-06-01 Thread Koen van de Sande
Koen van de Sande k...@tibed.net added the comment: This is listed as a known limitation of the Ext2 FS driver. From http://www.fs-driver.org/relnotes.html : === Running programs on an Ext2/Ext3 volume on Windows Vista Currently it is not possible to start a program on Vista if UAC

[issue5689] please support lzma compression as an extension and in the tarfile module

2010-05-25 Thread Koen van de Sande
Koen van de Sande k...@tibed.net added the comment: The XZ Utils website ( http://tukaani.org/xz/ ) states the following: The most interesting parts of XZ Utils (e.g. liblzma) are in the public domain. You can do whatever you want with the public domain parts. Some parts of XZ Utils (e.g

[issue7833] Bdist_wininst installers fail to load extensions built with Issue4120 patch

2010-04-27 Thread Koen van de Sande
Koen van de Sande k...@tibed.net added the comment: There should be no manifest embedded into wininst, because then the cases which Issue 4120 fixed (a CRT installed into a local folder, instead of system-wide, due to limited access rights), will 'break' again: the installer can

[issue7833] Bdist_wininst installers fail to load extensions built with Issue4120 patch

2010-04-27 Thread Koen van de Sande
Koen van de Sande k...@tibed.net added the comment: Concerning the patch: what happens when the developer already added /MANIFEST:NO to the flags, and the code deduces that MSVCR9 is the only runtime, e.g. the case where /MANIFEST:NO is in the flags twice? Does the linker handle this OK

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2009-10-29 Thread Koen van de Sande
Koen van de Sande k...@tibed.net added the comment: The MinGW breakage probably comes from the same issue as encountered in http://bugs.python.org/issue4120#msg80908 and #msg80909: the main application, which embeds Matplotlib, does not have a manifest for the MSVCR9 runtimes? That's a problem

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2009-10-13 Thread Koen van de Sande
Koen van de Sande k...@tibed.net added the comment: It may actually be enough to just place the Microsoft.VC90.CRT.manifest file into the Python folder (the one with python.exe and the CRT DLLs). I concur with what Christoph says, that is how the embedded installation works. However

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2009-10-07 Thread Koen van de Sande
Koen van de Sande k...@tibed.net added the comment: Thanks Christoph, those are two important fixes to the patch. I'm +1 on having this in the next 2.6 maintenance release. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2009-10-02 Thread Koen van de Sande
Koen van de Sande k...@tibed.net added the comment: Could msvc9compiler_stripruntimes.diff still be considered for inclusion in Python 2.6.3 (high priority?)? A lot of .pyd's of third-party extensions are getting dependencies on MSVCR90 added to the .pyd, which makes them not work

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2009-10-02 Thread Koen van de Sande
Koen van de Sande k...@tibed.net added the comment: It probably won't make 2.6.3 as the final is just out. But can we have it for 2.6.4? Here's a link to the relevant discussion on ImageSIG: http:// mail.python.org/pipermail/image-sig/2009-October/005918.html Looking at my local extensions

[issue5689] please support lzma compression as an extension and in the tarfile module

2009-04-20 Thread Koen van de Sande
Koen van de Sande k...@tibed.net added the comment: The LZMA implementation from 7-zip has been released as public domain (since version 4.62 / Nov 2008) in the LZMA SDK: http://www.7-zip.org/ sdk.html So, there shouldn't be a license issue for Windows. I am not sure if there are already

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2009-02-01 Thread Koen van de Sande
Koen van de Sande k...@tibed.net added the comment: @johan: no it is not a symptom of the same problem. The problem you are having is that the executable which is embedding Python does not have a manifest. If you add a manifest with a dependency on the VC90 runtimes to the main executable

[issue4710] [PATCH] zipfile.ZipFile does not extract directories properly

2008-12-21 Thread Koen van de Sande
Koen van de Sande k...@tibed.net added the comment: I'm no expert, but is it possible for ZIP files to have Windows-style path seperators ('\') as well? And is this new behavior desirable for existing code as well? It might break existing applications, so perhaps a new extractrecursive

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2008-10-24 Thread Koen van de Sande
Koen van de Sande [EMAIL PROTECTED] added the comment: OK, so the define is not going to work. For Python extensions built through distutils, the msvc9compiler_stripruntimes.diff patch will work: it will remove just the dependency on the VC90runtimes. It will leave other assembly dependencies

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2008-10-24 Thread Koen van de Sande
Koen van de Sande [EMAIL PROTECTED] added the comment: Ah, I wasn't thinking it through. It is fine for all .pyd of course, because they don't have any extra dependencies. I was thinking of DLLs with extra dependencies (of which there is one, TK85.dll). There, leaving out the manifest

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2008-10-22 Thread Koen van de Sande
Koen van de Sande [EMAIL PROTECTED] added the comment: _CRT_NOFORCE_MANIFEST sounds nice, but I'm having some trouble getting it to work for Python extensions. I'm still having manifests generated...? Can you show me how to use it? It is an undocumented option

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2008-10-21 Thread Koen van de Sande
Koen van de Sande [EMAIL PROTECTED] added the comment: Instead of reverting the patch for Issue 2563, I propose to strip the VC90 runtimes from the manifest (this will preserve other dependencies needed). I checked this by editing tk85.dll and replacing the dependency there with white-space

[issue4120] Do not embed manifest files in *.pyd when compiling with MSVC

2008-10-20 Thread Koen van de Sande
Koen van de Sande [EMAIL PROTECTED] added the comment: The TCL85.dll introduces a subtlety (actually it is TK85.dll). The MSVCRT90 is not the only dependency that can be in the manifest. The Windows.CommonControls.6.0 is used by TK85.dll. So, also for all Python extensions which have

[issue4022] 2.6 dependent on c:\python26\ on windows

2008-10-03 Thread Koen van de Sande
Koen van de Sande [EMAIL PROTECTED] added the comment: Have you tried restarting your machine after installing the Visual C++ runtime from Microsoft? These runtimes will sometimes only finish installing after a reboot. Also, putting them in System/System32 is not allowed by MSVCR90.dll

[issue4013] Python 2.6 Doc/tools folder bigger than in 2.6rc2

2008-10-02 Thread Koen van de Sande
New submission from Koen van de Sande [EMAIL PROTECTED]: The Doc/tools folder in the 2.6 distribution contains docutils, jinja, pygments, sphinx folders, which were not there in the 2.6rc2 .tar.bz2. Also, there is a roman.pyc in the Doc/tools folder. The difference in uncompressed size

[issue4014] Python-2.6-py2.6.egg-info contains Alpha reference

2008-10-02 Thread Koen van de Sande
New submission from Koen van de Sande [EMAIL PROTECTED]: In file lib/python2.6/lib-dynload/Python-2.6-py2.6.egg-info, after a fresh installation of Python 2.6 there are two lines for Development status both Alpha and Mature: Platform: Many Classifier: Development Status :: 3 - Alpha

[issue3936] Faulty suppression of 'as' keyword warning

2008-09-23 Thread Koen van de Sande
Koen van de Sande [EMAIL PROTECTED] added the comment: I was wondering why I didn't have any warnings in my code in 2.5, when it started failing with errors on import in 2.6. Now I know. -- nosy: +koen ___ Python tracker [EMAIL PROTECTED] http

[issue1074] python3.0-config script does not run on py3k

2007-08-31 Thread Koen van de Sande
New submission from Koen van de Sande: The python3.0-config script, installed into the py3k bin folder, does not run on Python 3.0a1, because of the syntax change in the print statement. Possibly there are other compatibility issues. -- components: None messages: 55538 nosy: koen