This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author paul.j3
Recipients berker.peksag, bethard, mbussonn, paul.j3, serhiy.storchaka
Date 2015-06-03.17:30:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Off hand I don't see a problem with this patch (but I haven't tested it yet).

But I have a couple of cautions:

The docs say, regarding the Namespace class:

> This class is deliberately simple, just an object subclass with a readable string representation.

This patch improves the 'readable' part, but adds some complexity.

The docs also note that the user can provide their own namespace object, and by implication, a custom Namespace class with this improved '__repr__'.

The Namespace '__repr__' is mainly of value during code development, especially when trying ideas in an interactive shell.  It's unlikely that you would want to show the whole namespace to your end user.  So even if your final API requires funny characters, you don't need to use them during development.
Date User Action Args
2015-06-03 17:30:31paul.j3setrecipients: + paul.j3, bethard, berker.peksag, serhiy.storchaka, mbussonn
2015-06-03 17:30:31paul.j3setmessageid: <>
2015-06-03 17:30:31paul.j3linkissue24360 messages
2015-06-03 17:30:31paul.j3create