Message160623
> - the function generating the flags should be exported (with a private
> name), so that it can be reused by Lib/test/[test_]support.py. Duplicate
> code is error-prone, especially when enumerating command-line flags,
> attribute names...
Failure to build _multiprocessing will mean that multiprocessing cannot be imported. So if the function goes somewhere in multiprocessing then it makes running the test suite with multiple processes dependent on the building of _multiprocessing. Not sure if that is much of a problem since one can just run the test suite normally.
Also I don't think "-i" (inspect/interactive) should be passed on: a child process's stdin is os.devnull.
BTW, why isn't the use of "-u" (unbuffered stdout, stderr) reflected in sys.flags? |
|
Date |
User |
Action |
Args |
2012-05-14 13:28:38 | sbt | set | recipients:
+ sbt, amaury.forgeotdarc, pitrou, vstinner, jnoller, neologix, thebits |
2012-05-14 13:28:37 | sbt | set | messageid: <1337002117.98.0.345318230643.issue12098@psf.upfronthosting.co.za> |
2012-05-14 13:28:37 | sbt | link | issue12098 messages |
2012-05-14 13:28:37 | sbt | create | |
|