[New-bugs-announce] [issue5450] test_tcl testLoadTk fails if DISPLAY defined but connect fails, instead of being skipped

[R. David Murray]

New submission from R. David Murray <rdmurray at bitdance.com>:

If the DISPLAY environment variable is set, the test_tcl test
'testLoadTk' gives a traceback.  In the same circumstance, test_tk and
test_ttkguionly display the error and are skipped.  Although this is a
nit rather than a problem, for consistencies sake I think the testLoadTk
test should also be skipped rather than show up as a failure.  I've
attached a patch against the trunk that does this, with the caveat that
it is an individual testcase being skipped so it doesn't get recorded in
the 'skipped tests' summary.  I don't think this is a problem since
test_tk will likely show up in the skipped tests if this one is skipped,
and also there are circumstances in which testLoadTkFailure is skipped
completely silently.

Perhaps the real problem is that the tk tests should be in test_tk
instead of test_tcl?

----------
components: Tests, Tkinter
files: test_tcl.patch
keywords: patch
message_count: 1.0
messages: 83339
nosy: bitdancer
nosy_count: 1.0
severity: normal
status: open
title: test_tcl testLoadTk fails if DISPLAY defined but connect fails, instead of being skipped
type: behavior
versions: Python 2.6, Python 3.0, Python 3.1
Added file: http://bugs.python.org/file13273/test_tcl.patch

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5450>
_______________________________________