[issue2975] VS8 include dirs grow without bound

Jim Kleckner [EMAIL PROTECTED] added the comment: Here is the equals sign fix as a separate patch file. Added file: http://bugs.python.org/file11343/equalsInEnv.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2975

[issue2975] VS8 include dirs grow without bound

Jim Kleckner [EMAIL PROTECTED] added the comment: Any hope for these two patches being applied? ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2975

[issue2975] VS8 include dirs grow without bound

Jim Kleckner [EMAIL PROTECTED] added the comment: Yes, much better. I should have read into the interior of the discussion rather than just the edges... Thanks! ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2975

[issue2975] VS8 include dirs grow without bound

Jim Kleckner [EMAIL PROTECTED] added the comment: Any new thoughts on this? I had to patch my local copy again after a reinstall. It would be nice to fix it upstream. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2975

[issue2975] VS8 include dirs grow without bound

Jim Kleckner [EMAIL PROTECTED] added the comment: Sorry, posted too quickly. Actually, the problem was a little different. There was an environment variable with '=' characters in it. Here is a patch to deal with that: --- msvc9compiler.py.orig 2008-07-23 16:13:25.248438400 -0700

[issue2975] VS8 include dirs grow without bound

Jim Kleckner [EMAIL PROTECTED] added the comment: Actually, now that I think about it a little more, it seems like very bad practice to change the process environment variables as a side effect. A better solution would be to keep a variable for the required ones that is modified as necessary

[issue2975] VS8 include dirs grow without bound

Jim Kleckner [EMAIL PROTECTED] added the comment: Talk about tunnel vision... The code is right next to it! It is the include paths that are growing without bound (and presumably the LIBPATH as well). The test case is the Cython unit tests. They run until the include variable generates

[issue2256] Install failure of 2.6a1 on Windows XP without VS8 installed

Jim Kleckner [EMAIL PROTECTED] added the comment: I hadn't seen any comment here that I should try it again until your question (that was why the ping). I did try it again and my application worked. Thanks! __ Tracker [EMAIL PROTECTED] http://bugs.python.org

[issue2256] Install failure of 2.6a1 on Windows XP without VS8 installed

Jim Kleckner [EMAIL PROTECTED] added the comment: Ping. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2256 __ ___ Python-bugs-list mailing list Unsubscribe: http

[issue2256] Install failure of 2.6a1 on Windows XP without VS8 installed

Jim Kleckner [EMAIL PROTECTED] added the comment: It appears that issue2563 may be a dependency. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2256 __ ___ Python-bugs-list

[issue2256] Install failure of 2.6a1 on Windows XP without VS8 installed

Jim Kleckner added the comment: I uninstalled and re-ran the install without the compile all selected. The install didn't report errors. running: python -c import test.testall results in a traceback with the message: import _socket ImportError: DLL load failed: The system could

[issue2256] Install failure of 2.6a1 on Windows XP without VS8 installed

New submission from Jim Kleckner: When I install 2.6a1 onto a Windoze machine 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