[issue12717] ConfigParser._Chainmap error in 2.7.2

2011-08-09 Thread Mike Garabedian
Mike Garabedian added the comment: Happy to help! Raymond - I came across this issue while reviewing notes from your OSCON Advanced Python talk - thanks for the great tutorial! -- ___ Python tracker

[issue12717] ConfigParser._Chainmap error in 2.7.2

2011-08-09 Thread Raymond Hettinger
Raymond Hettinger added the comment: Fixed. Thanks for the report. Éric, the test suite didn't catch this because the error wasn't user visible -- the chainmap is only used internally and only __getitem__ was needed. -- resolution: -> fixed status: open -> closed __

[issue12717] ConfigParser._Chainmap error in 2.7.2

2011-08-09 Thread Roundup Robot
Roundup Robot added the comment: New changeset 7d5a37ce42d5 by Raymond Hettinger in branch '2.7': Issue 12717: Fix-up an earlier backport in ConfigParser. http://hg.python.org/cpython/rev/7d5a37ce42d5 -- nosy: +python-dev ___ Python tracker

[issue12717] ConfigParser._Chainmap error in 2.7.2

2011-08-09 Thread Raymond Hettinger
Raymond Hettinger added the comment: Thanks, I'll fix that shortly. -- priority: normal -> high ___ Python tracker ___ ___ Python-bug

[issue12717] ConfigParser._Chainmap error in 2.7.2

2011-08-09 Thread Éric Araujo
Éric Araujo added the comment: Thanks for catching this. I’m baffled that the test suite did not catch that. -- assignee: -> rhettinger nosy: +eric.araujo stage: -> test needed type: compile error -> behavior ___ Python tracker

[issue12717] ConfigParser._Chainmap error in 2.7.2

2011-08-09 Thread Mike Garabedian
New submission from Mike Garabedian : Issue 11089 submitted a patch to 3.2 and 2.7 to address performance concerns with the latest updates to ConfigParser. In the implementation for 2.7.2, this patch was misapplied in the keys() function on line 573: for mapping in self_maps: should be: