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

Roundup Robot 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 ___ Python tracker

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

Michael Foord 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 -> committed/rejected status: ope

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

Michael Foord 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 ___ Python track

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

Changes by Łukasz Langa : -- nosy: +michael.foord ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

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

Mark Lawrence 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

Łukasz Langa 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

Mark Lawrence 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 backported. -- nosy: +B

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

Łukasz Langa 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, the code change

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

Changes by Martin v. Löwis : -- 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

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

New submission from David M. Beazley : 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. For example, shouldn't NoOpt