Re: [Python-Dev] 3.2b2 fails test suite on (my) Windows XP

2011-01-12 Thread David Bolen
Brian Curtin writes: > http://bugs.python.org/issue9116 covers this issue. > > The reason it doesn't fail on any of the build slaves is because they modify > a registry value for Windows Error Reporting to not display the pop-up > window, or at least mine does. I think I got the idea from one of

Re: [Python-Dev] 3.2b2 fails test suite on (my) Windows XP

2011-01-07 Thread Terry Reedy
On 1/6/2011 11:54 PM, Nick Coghlan wrote: On Thu, Jan 6, 2011 at 4:00 PM, Terry Reedy wrote: Does it behave itself if you add "-x test_capi" to the command line? No, it gets worse. Really. Let me summarize a long post. Run 1: normal (as above) Process stops at capi test with Windows error me

Re: [Python-Dev] 3.2b2 fails test suite on (my) Windows XP

2011-01-06 Thread Nick Coghlan
On Thu, Jan 6, 2011 at 4:00 PM, Terry Reedy wrote: >> Does it behave itself if you add "-x test_capi" to the command line? > > No, it gets worse. Really. > Let me summarize a long post. > > Run 1: normal (as above) > Process stops at capi test with Windows error message. > Close command prompt win

Re: [Python-Dev] 3.2b2 fails test suite on (my) Windows XP

2011-01-06 Thread Dj Gilcrease
On Thu, Jan 6, 2011 at 1:00 AM, Terry Reedy wrote: > On 1/5/2011 8:59 PM, Nick Coghlan wrote: > Run 3: -x test_capi test_concurrent_futures > Instead of the normal output I expected, I got some of the craziest stuff I > have ever seen. Things like > " >    assert main_name not in sys.modules, main

Re: [Python-Dev] 3.2b2 fails test suite on (my) Windows XP

2011-01-06 Thread Antoine Pitrou
On Wed, 5 Jan 2011 17:56:53 -0600 Brian Curtin wrote: > > http://bugs.python.org/issue9116 covers this issue. > > The reason it doesn't fail on any of the build slaves is because they modify > a registry value for Windows Error Reporting to not display the pop-up > window, or at least mine does.

Re: [Python-Dev] 3.2b2 fails test suite on (my) Windows XP

2011-01-05 Thread Terry Reedy
On 1/5/2011 8:59 PM, Nick Coghlan wrote: On Thu, Jan 6, 2011 at 9:47 AM, Terry Reedy wrote: To test Brett's test running instruction, I ran python -m test # not ./Python! in a Command Prompt window Does it behave itself if you add "-x test_capi" to the command line? No, it gets worse. Reall

Re: [Python-Dev] 3.2b2 fails test suite on (my) Windows XP

2011-01-05 Thread Nick Coghlan
On Thu, Jan 6, 2011 at 9:47 AM, Terry Reedy wrote: > To test Brett's test running instruction, I ran > python -m test # not ./Python! > in a Command Prompt window Does it behave itself if you add "-x test_capi" to the command line? Cheers, Nick. -- Nick Coghlan   |   ncogh...@gmail.com   |   B

Re: [Python-Dev] 3.2b2 fails test suite on (my) Windows XP

2011-01-05 Thread Brian Curtin
On Wed, Jan 5, 2011 at 17:56, Brian Curtin wrote: > On Wed, Jan 5, 2011 at 17:47, Terry Reedy wrote: > >> To test Brett's test running instruction, I ran >> python -m test # not ./Python! >> in a Command Prompt window >> --- >> Microsoft Windows XP [Version 5.1.2600] >> >> == CPython 3.2b2 (r32b

Re: [Python-Dev] 3.2b2 fails test suite on (my) Windows XP

2011-01-05 Thread Brian Curtin
On Wed, Jan 5, 2011 at 17:47, Terry Reedy wrote: > To test Brett's test running instruction, I ran > python -m test # not ./Python! > in a Command Prompt window > --- > Microsoft Windows XP [Version 5.1.2600] > > == CPython 3.2b2 (r32b2:87398, Dec 19 2010, 22:51:00) > [MSC v.1500 32 bit (Intel)

[Python-Dev] 3.2b2 fails test suite on (my) Windows XP

2011-01-05 Thread Terry Reedy
To test Brett's test running instruction, I ran python -m test # not ./Python! in a Command Prompt window --- Microsoft Windows XP [Version 5.1.2600] == CPython 3.2b2 (r32b2:87398, Dec 19 2010, 22:51:00) [MSC v.1500 32 bit (Intel)] == Windows-XP-5.1.2600-SP3 little-endian == c:\docume~1\te