Zachary Ware added the comment:
There are a couple in pickletester, one in test_io, a few in test_reprlib, and
the ones in the patch from test_minidom; some 10 test methods in total that
I've found and remembered. I suppose with that few, it would be best to just
open issues for each test
Ezio Melotti added the comment:
I don't think a new option for regrtest is necessary.
I'm also not sure expected failure is a good idea -- in some cases it might be
better to report a skip or an error.
Do you have other examples where this can be used? If there aren't many
occurrences we
Antoine Pitrou added the comment:
Indeed, this doesn't sound like a terrific idea to me.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19597
___
New submission from Zachary Ware:
Some tests in the test suite are not implemented for one reason or another, and
most of these are defined simply as def test_thats_not_implemented(self):
pass, possibly with a comment meant to be a reminder to implement it. This
patch adds a decorator to
Zachary Ware added the comment:
This patch takes the idea a little further, adding a command line option to
regrtest, '--failnoimpl' (it could use a better name).
With this option specified any test decorated by support.not_implemented will
not be marked as an expected failure, allowing the
