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

Steven Bethard steven.bethard at gmail.com
Mon Nov 1 15:59:03 CET 2010


On Mon, Nov 1, 2010 at 2:57 PM, Guido van Rossum <guido at python.org> wrote:
> On Mon, Nov 1, 2010 at 7:53 AM, Michael Foord <fuzzyman at voidspace.org.uk> wrote:
>> On 01/11/2010 14:48, Steven Bethard wrote:
>>> 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?
>>
>> Isn't it better to add the missing elements - what is the problem with that
>> approach?
>
> Agreed, that's what I would do.

Ok, sounds good.

> It is also possible to write automated tests that flag likely missing
> symbols in __all__ (as well as symbols in __all__ missing from the
> module).

Yep, I plan on doing that. I already had a test something like this to
remind me how I broke __all__ before. ;-)

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


More information about the Python-Dev mailing list