[Python-Dev] Matching __all__ to doc: bugfix or enhancement?
Terry Reedy
tjreedy at udel.edu
Fri Mar 15 08:09:58 CET 2013
More information about the Python-Dev mailing list
Fri Mar 15 08:09:58 CET 2013
- Previous message: [Python-Dev] Matching __all__ to doc: bugfix or enhancement?
- Next message: [Python-Dev] Followup - Re: Bad python 2.5 build on OSX 10.8 mountain lion
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 3/15/2013 12:15 AM, Guido van Rossum wrote: > 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 *. :-) Thanks all. Pushed to 3.4 only. -- Terry Jan Reedy
- Previous message: [Python-Dev] Matching __all__ to doc: bugfix or enhancement?
- Next message: [Python-Dev] Followup - Re: Bad python 2.5 build on OSX 10.8 mountain lion
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list