A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2007-July/074051.html below:

[Python-Dev] Cygwin: Problem detecting subprocess termination after _spawn_posix in distutils?

[Python-Dev] Cygwin: Problem detecting subprocess termination after _spawn_posix in distutils? [Python-Dev] Cygwin: Problem detecting subprocess termination after _spawn_posix in distutils?"Martin v. Löwis" martin at v.loewis.de
Tue Jul 31 23:44:33 CEST 2007
> It would be really nice if test_distutils showed any failures, but it 
> doesn't so any assistance would be welcome. At this point I can't even 
> replicate the failure in a simpler test :-(

My guess is that it's the environment; if not that, the working
directory. Assuming you have already instrumented
ccompiler.CCompiler.spawn, I suggest to dump os.environ and
print os.getcwd(). Assuming you really meant that you run under
Cygwin Python (instead of just using --compiler), you might
want to instrument spawn._spawn_posix instead.

When you say you extracted _spawn_all from distutils/spawn.py:
what version of Python are you talking about? I can't find
_spawn_all in the sources of 2.5.x, or 2.6.

Regards,
Martin
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4