[Python-Dev] okay to remove argparse.all? (original) (raw)

Michael Foord fuzzyman at voidspace.org.uk
Mon Nov 1 15:53:24 CET 2010

On 01/11/2010 14:48, Steven Bethard wrote:

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?

Isn't it better to add the missing elements - what is the problem with that approach?

Not defining all will mean that "from argparse import *" will also export all the modules you import (copy, os, re, sys, textwrap).

All the best,

Michael

Steve

--

http://www.voidspace.org.uk/

READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.

More information about the Python-Dev mailing list