Matching __all__ to doc: bugfix or enhancement?
The timeit doc describes four public attributes. The current timeit.__all__ only lists one. http://bugs.python.org/issue17414 proposes to expand __all__ to include all four: -__all__ = ["Timer"] +__all__ = ["Timer", "timeit", "repeat", "default_timer"] The effect of the change is a) help(timit) will mention the three functions as well as the class; b) IDLE's attribute completion box* will list all four instead just Timer; c) unknow other users of .__all__ will see the expanded list, for better or worse. * Typing 'xxx.' and either waiting or typing cntl-space brings up a listbox of attributes to select from. Is the code change an all-version bugfix or a default-only enhancement? I can see it both ways, but a decision is required to act. PS: I think the devguide should gain a new 'Behavior versus Enhancement' section after the current "11.1.2. Type" to clarify issues like this. -- Terry Jan Reedy
On Thu, Mar 14, 2013 at 9:33 PM, Terry Reedy <tjreedy@udel.edu> wrote:
Is the code change an all-version bugfix or a default-only enhancement? I can see it both ways, but a decision is required to act.
This is actually backward-incompatible, so should not be considered a simple bugfix. If determined to be desirable, it should not be applied to any version before 3.4. -Fred -- Fred L. Drake, Jr. <fred at fdrake.net> "A storm broke loose in my mind." --Albert Einstein
So it's a new feature, albeit a small one. I do see that it shouldn't be backported, but I don't see any worries about doing it in 3.4. Adding new functions/classes/constants to modules happens all the time, and we never give a second thought to users of import *. :-) On Thu, Mar 14, 2013 at 6:54 PM, Eli Bendersky <eliben@gmail.com> wrote:
-- --Guido van Rossum (python.org/~guido)
On Thu, Mar 14, 2013 at 9:33 PM, Terry Reedy <tjreedy@udel.edu> wrote:
Is the code change an all-version bugfix or a default-only enhancement? I can see it both ways, but a decision is required to act.
This is actually backward-incompatible, so should not be considered a simple bugfix. If determined to be desirable, it should not be applied to any version before 3.4. -Fred -- Fred L. Drake, Jr. <fred at fdrake.net> "A storm broke loose in my mind." --Albert Einstein
So it's a new feature, albeit a small one. I do see that it shouldn't be backported, but I don't see any worries about doing it in 3.4. Adding new functions/classes/constants to modules happens all the time, and we never give a second thought to users of import *. :-) On Thu, Mar 14, 2013 at 6:54 PM, Eli Bendersky <eliben@gmail.com> wrote:
-- --Guido van Rossum (python.org/~guido)
participants (4)
-
Eli Bendersky -
Fred Drake -
Guido van Rossum -
Terry Reedy