Changes by Austin Bingham :
--
nosy: +Austin Bingham
___
Python tracker
<http://bugs.python.org/issue26680>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Austin Bingham:
When passed a weakref.proxy to a legitimate sequence, reversed() throws a
TypeError complaining that its argument isn't a sequence. Perhaps this is the
expected behavior, but it's surprising to at least me and the few others I've
spoke
Changes by Austin Bingham :
--
nosy: +abingham
___
Python tracker
<http://bugs.python.org/issue13807>
___
___
Python-bugs-list mailing list
Unsubscribe:
Austin Bingham added the comment:
Yes, in some sense that's what I'm thinking of. But one problem with
this straightforward approach is that it doesn't scale well. If I've
got many TestCases, each if which I want to parameterize, I have to
create subclasses for each paramete
Austin Bingham added the comment:
OK, I created issue 12600 for dealing with parameterized TestCases as
opposed to individual tests.
On Wed, Jul 20, 2011 at 4:03 PM, R. David Murray wrote:
> Unless someone sees a clever way to implement both with the same mechanism,
> parameterizin
New submission from Austin Bingham :
In the discussion about adding support for parameterized tests (issue 7897), it
seemed clear that parameterizing individual tests was a different issue from
parameterizing TestCases. This, then, is a request to support parameterization
of TestCases.
The
Austin Bingham added the comment:
Has a decision been made to implement some form of parametric tests? Is working
being done?
Along with parameterizing individual test methods, I'd also like to throw out a
request for parametric TestCases. In some cases I find that I want the behavio
New submission from Austin Bingham :
traceback.print_exception() will throw an AttributeException if `value` is None
and `chain` is True. This is because `_iter_chain` assumes that the exception
object has a `__cause__` attribute. You can trigger this by trying for format a
non-existent
