RetroSearch Browse

Tue Nov 23 13:45:53 CET 2004 · https://mail.python.org/pipermail/python-dev/2004-November/050089.html

On Sat, Nov 20, 2004 at 10:06:37AM -0500, Jason Tishler wrote:
> > If you (or anyone else) could check that the unit tests work on
> > Cygwin for you, that would make me more certain that this is just a
> > problem with my own Cygwin setup, and not related to anything in
> > 2.4c1 that wasn't in 2.4b1.
> 
> I just upgraded one of my machines to Cygwin 1.5.12, but I did not
> upgrade the other packages.  I get the following results:
> 
>     failures:
> 
>         test_shutil (passed under older Cygwin and/or Python versions)
>         test_subprocess (new test)
>         test_tcl (new test)
> 
>     hangs:
> 
>         test_threaded_import (passed under older Cygwin and/or ...
> 
> I will investigate the above and report back.

AFAICT, the above (with possibly one exception) are due to Cygwin bugs.
I can provide more details if anyone is interested.

On Sat, Nov 20, 2004 at 01:03:42AM +1000, Nick Coghlan wrote:
> This was meant to be a "Yup, she's all good" exercise before 2.4 final
> goes out the door.

IMO, "Yup, she's all good!" :,)

The test_tcl test case is failing under Cygwin because it expects
loadtk() to fail if the DISPLAY environment variable is not set.
However, under Cygwin we have the following:

    >>> import os, Tkinter
    >>> del os.environ['DISPLAY']
    >>> Tkinter.Tcl().loadtk()
    >>>

The above works because Cygwin's Tcl/Tk renders directly on the Windows
GDI instead of going through an X Server.  Can I submit a patch to
test_tcl to skip this test as is done for win and darwin?

Thanks,
Jason

-- 
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2004-November/050089.html below:

[Python-Dev] Current CVS, Cygwin and "make test"