[issue4686] Exceptions in ConfigParser don't set .args

2012-01-23 Thread Roundup Robot
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset 8e091e36fc80 by Łukasz Langa in branch '2.7': Fixes #4686. Reverts redundant picklability code from r74544. http://hg.python.org/cpython/rev/8e091e36fc80 -- nosy: +python-dev

[issue4686] Exceptions in ConfigParser don't set .args

2010-07-26 Thread Michael Foord
Michael Foord mich...@voidspace.org.uk added the comment: Patch doesn't apply cleanly to 3.1 or earlier. As it is *arguably* a new feature rather than a bugfix I'm closing the issue. I certainly wouldn't argue against someone else backporting though... -- stage: commit review -

[issue4686] Exceptions in ConfigParser don't set .args

2010-07-25 Thread Łukasz Langa
Changes by Łukasz Langa luk...@langa.pl: -- nosy: +michael.foord ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4686 ___ ___ Python-bugs-list

[issue4686] Exceptions in ConfigParser don't set .args

2010-07-25 Thread Michael Foord
Michael Foord mich...@voidspace.org.uk added the comment: Committed revision 83150. Still needs backporting to 3.1, 2.7 and possibly even 2.6. -- assignee: - michael.foord resolution: - accepted stage: patch review - commit review versions: +Python 2.6

[issue4686] Exceptions in ConfigParser don't set .args

2010-07-24 Thread Mark Lawrence
Mark Lawrence breamore...@yahoo.co.uk added the comment: Tests failed after patching test file, all passed after patching the code on Windows against 3.2. The patch looks simple and clean so I don't see why it can't be committed. As this is a behaviour issue the code should also be

[issue4686] Exceptions in ConfigParser don't set .args

2010-07-24 Thread Łukasz Langa
Łukasz Langa luk...@langa.pl added the comment: Thanks, Mark. Should I do the backporting or do you have some technology/process for this? I can do the backport as well if it doesn't require SVN commit access. I would need some help because it would be my first backport :) --

[issue4686] Exceptions in ConfigParser don't set .args

2010-07-24 Thread Mark Lawrence
Mark Lawrence breamore...@yahoo.co.uk added the comment: Łukasz, no problem. It would be my first backport too! :) I think that it's best left to the committers as they've well used to doing things like this. -- ___ Python tracker

[issue4686] Exceptions in ConfigParser don't set .args

2010-07-23 Thread Łukasz Langa
Łukasz Langa luk...@langa.pl added the comment: Sound argument. I've prepared a patch for Py3k that adds `args` for all exceptions. Unit tests were modified as to check whether the `args` are set correctly (which helped finding a couple of flaky assertions in the tests themselves :)). Brett,

[issue4686] Exceptions in ConfigParser don't set .args

2008-12-20 Thread Martin v. Löwis
Changes by Martin v. Löwis mar...@v.loewis.de: -- versions: -Python 2.1.1, Python 2.1.2, Python 2.2, Python 2.2.1, Python 2.2.2, Python 2.2.3, Python 2.3, Python 2.4, Python 2.5, Python 2.5.3 ___ Python tracker rep...@bugs.python.org

[issue4686] Exceptions in ConfigParser don't set .args

2008-12-17 Thread David M. Beazley
New submission from David M. Beazley beaz...@users.sourceforge.net: The ConfigParser module defines a variety of custom exceptions, many of which take more than one argument (e.g., InterpolationError, NoOptionError, etc.). However, none of these exceptions properly set the .args attribute.