New submission from anatoly techtonik <techto...@gmail.com>:
The following command is broken on Python 2.5/2.6
python -m unittest test_file
It outputs
----------------------------------------------------------------------
Ran 0 tests in 0.000s
OK
But in Python 2.7 the same command works
----------------------------------------------------------------------
Ran 1 tests in 0.000s
OK
It is even more confusing with test class method on command line:
python26 -m unittest test_file.SomeTest
Traceback (most recent call last):
...
File "C:\~env\Python26\lib\unittest.py", line 598, in loadTestsFromName
test = obj()
File "C:\~env\Python26\lib\unittest.py", line 216, in __init__
(self.__class__, methodName)
ValueError: no such test method in <class 'test_file.SomeTest'>: runTest
---
I know that our <...> policy denies backporting such fixes to Python 2.5/2.6,
but such things that make an illusion that they work while in fact they never
did - see #6514, make Python really suxx. I can feel user frustration while
trying to maintain 2.6 compatibility and wasting time trying to run test suite.
I wouldn't mind if `-m unittest` won't work in non-supported versions, but it
should at least point to bug report.
(if I'll ever switch to Ruby - this one will definitely be in the list reasons)
----------
components: Tests
messages: 133449
nosy: techtonik
priority: normal
severity: normal
status: open
title: 'unittest -m' should not pretend it works on Python 2.5/2.6
type: behavior
versions: Python 2.5, Python 2.6
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue11819>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
