Davin Potts added the comment: @berker: I would have said this should not be marked an enhancement as the proposed solution (in the patch) is to correct the errors in the documentation to accurately describe the current implemented behavior. Does that make sense? Whatever label we give it, do you think my logic (described in my comments on this issue) for why it is best to fix it this way makes sense to you? ---------- _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue23484> _______________________________________