Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-November/105147.html below:

[Python-Dev] okay to remove argparse.__all__?

• Previous message: [Python-Dev] Change to logging Formatters: support for alternative format styles
• Next message: [Python-Dev] okay to remove argparse.__all__?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I think the easiest and most sensible way to address
http://bugs.python.org/issue9353 is to simply remove the __all__
definition from argparse - everything that doesn't start with an
underscore in the module is already meant to be exposed.

But then I wonder - is __all__ considered part of the public API of a
module? Or is it okay to just remove it and assume that no one should
have been accessing it directly anyway?

Steve
-- 
Where did you get that preposterous hypothesis?
Did Steve tell you that?
        --- The Hiphopopotamus

• Previous message: [Python-Dev] Change to logging Formatters: support for alternative format styles
• Next message: [Python-Dev] okay to remove argparse.__all__?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4