Barry Warsaw <[EMAIL PROTECTED]> writes:
> On Feb 24, 2008, at 1:57 PM, Martin v. Löwis wrote:
>
>>> It very well might. See Christian Heimes's follow up re: Windows
>>> builds. OTOH, I'm okay if at least for the alphas, the binary
>>> builds lag behind the source releases, though I'd like
"Brett Cannon" <[EMAIL PROTECTED]> writes:
> Also realize all of the right people have been consulted on this stuff
> (e.g., the web SIG about the urllib package). So please do not think
> that something that seems drastic (e.g., the removal of all
> Mac-specific modules) was taken lightly when in
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
>> These messageboxes of course hang the tests on the windows build servers,
>> so probably it would be good if they could be disabled completely.
>
> I think this will be very difficult to achieve.
Could the tests be run beneath a shim process that u
David Bolen <[EMAIL PROTECTED]> writes:
> "Martin v. Löwis" <[EMAIL PROTECTED]> writes:
>
>>> These messageboxes of course hang the tests on the windows build servers,
>>> so probably it would be good if they could be disabled completely.
>&g
On 8/29/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > If I
> > remember correctly the error mode is inherited, so an independent
> > small exec module could reset the mode, and execute the normal test
> > sequence as a child process.
>
> It would also be possible to put that into the interpr
"Amaury Forgeot d'Arc" <[EMAIL PROTECTED]> writes:
> Note that there is currently only one Windows buildbot to watch - and
> it is a win64. Most tests that fail there pass on my machine.
> Nevertheless, the log is much smaller than before.
There's an offer of mine to host an additional Windows (w
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> Are you saying that calling SetErrorMode also makes the VC _ASSERT
> message boxes go away?
I don't believe it should, no. The assert message boxes are from the VC
runtime, whereas the OS error dialogs are from, well, the OS :-)
Certainly in my ma
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
>> So, an environment variable would be useful, but maybe there should also be
>> a Python function available that calls set_error_mode().
>> sys.set_error_mode()?
>
> Even though this would be somewhat lying - I'd put it into
> msvcrt.set_error_mode
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> However, we can't use pywin32 on the buildbot slaves - it's not
> installed.
Agreed, thus my original suggestion of a standalone wrapper executable
(or using ctypes). But for end users of Python on Windows, this is a
direct Windows-specific API wra
