Neal Norwitz wrote: > On 12/23/05, Tim Peters <[EMAIL PROTECTED]> wrote: > >>> http://docs.python.org/dev/results/ >> >>Wow! You get no test failures! I guess nobody tests on Windows >>anymore. I've been getting test failures for months, and just > > > Hmmm, I thought others were running the tests on Windows too. There > was one report on Nov 22 about running Purify on Windows 2k (subject: > ast status, memory leaks, etc). He had problems with a stack overflow > in test_compile. He was going to disable the test and re-run. I > never heard back though. Based on that info, I would guess that > test_builtin was working on Win 2k on Nov 22. > > >>_assumed_ this was known damage everywhere so was waiting for someone >>else to fix it ;-) (A parenthentical question: is there a reason you >>don't pass -uall to regrtest.py?) > [...] I suppose this might be evidence in support of the arguments for trying to make Python compile on Windows under an open-source toolset.
The reason *I* don't test under Windows is because I can't build under Windows, so I only run Python installed from packaged installers. Alternatively, is there any mileage in trying to either get Sourceforge to provide Windows machines in the compile farm, or get Microsoft to provide more software fee to Windows testers? regards Steve -- Steve Holden +44 150 684 7255 +1 800 494 3119 Holden Web LLC www.holdenweb.com PyCon TX 2006 www.python.org/pycon/ _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
