[Python-Dev] subprocess module test failure when --with-pydebug

Barry Warsaw barry at python.org
Tue Oct 12 21:31:55 CEST 2004

The new subprocess module test is not compatible with a Python built
--with-pydebug because the [xxxx refs] output breaks the comparison.

I've recently been thinking that it would be nice if that [xxxx refs]
output could be suppressed with an envar or a command line switch. 
FWIW, I generally build our embedding product with a --with-pydebug
built Python and that output breaks our unit tests too.  I work around
this by suppressing the stderr comparison in our testing framework.

Once we decide to do it, and what to wrap that call in, it's likely a
one or two line change to pythonrun.c.  Does one of the existing envars
make sense to use?

Barring any change here, we need to at least make sure the subprocess
test doesn't fail for a debug build.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 307 bytes
Desc: This is a digitally signed message part
Url : http://mail.python.org/pipermail/python-dev/attachments/20041012/f96bafc2/attachment.pgp

More information about the Python-Dev mailing list