[issue19359] reversed() does not work with weakref.proxy of sequences

2013-10-23 Thread Austin Bingham
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 spoken with about

[issue13807] logging.Handler.handlerError() may raise AttributeError in traceback.print_exception()

2012-01-18 Thread Austin Bingham
Changes by Austin Bingham austin.bing...@gmail.com: -- nosy: +abingham ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13807 ___ ___ Python-bugs

[issue12600] Support parameterized TestCases in unittest

2011-07-23 Thread Austin Bingham
Austin Bingham austin.bing...@gmail.com 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

[issue7897] Support parametrized tests in unittest

2011-07-20 Thread Austin Bingham
Austin Bingham austin.bing...@gmail.com 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

[issue12600] Support parameterized TestCases in unittest

2011-07-20 Thread Austin Bingham
New submission from Austin Bingham austin.bing...@gmail.com: 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

[issue7897] Support parametrized tests in unittest

2011-07-20 Thread Austin Bingham
Austin Bingham austin.bing...@gmail.com 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 rep...@bugs.python.org wrote: Unless someone sees a clever way to implement both

[issue10805] traceback.print_exception throws AttributeError when exception is None

2011-01-02 Thread Austin Bingham
New submission from Austin Bingham austin.bing...@gmail.com: 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