[issue10894] Making stdlib APIs private

2016-03-23 Thread SilentGhost
Changes by SilentGhost : -- resolution: -> rejected stage: patch review -> resolved status: open -> closed type: -> behavior ___ Python tracker

[issue10894] Making stdlib APIs private

2016-03-22 Thread Raymond Hettinger
Raymond Hettinger added the comment: Much of this is already in PEP 8 and doesn't need repeating. Also, the tone is somewhat judgmental, heavy handed, restrictive, and over-broad for my tastes. The last part seems to imply that we're going to change existing code in a way that may break user

[issue10894] Making stdlib APIs private

2016-03-22 Thread SilentGhost
SilentGhost added the comment: I wonder if the devguide would be a more suitable place for these guidelines. Here is the patch that adds them to stdblibchanges.rst -- keywords: +patch stage: needs patch -> patch review versions: +Python 3.5, Python 3.6 -Python 3.4 Added file:

[issue10894] Making stdlib APIs private

2013-01-11 Thread Brett Cannon
Brett Cannon added the comment: So I just closed the dependency on this issue as I figured the potential code breakage wasn't worth this (plus the referenced TODO item from the devguide is gone and was never turned into a proper task). Now the question becomes do the guidelines SilentGhost

[issue10894] Making stdlib APIs private

2011-01-12 Thread SilentGhost
New submission from SilentGhost ghost@gmail.com: Following suggestion in the Developers Guide (http://docs.python.org/devguide/#index-5) and the rules proposed by Michael Foord (http://mail.python.org/pipermail/python-dev/2010-November/105476.html): If a module or package

[issue10894] Making stdlib APIs private

2011-01-12 Thread SilentGhost
SilentGhost ghost@gmail.com added the comment: Depends on issue10895 -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10894 ___ ___

[issue10894] Making stdlib APIs private

2011-01-12 Thread Benjamin Peterson
Changes by Benjamin Peterson benja...@python.org: -- dependencies: +Private stdlib API: getopt, getpass, glob, gzip, genericpath, gettext ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10894

[issue10894] Making stdlib APIs private

2011-01-12 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10894 ___ ___ Python-bugs-list

[issue10894] Making stdlib APIs private

2011-01-12 Thread Brett Cannon
Brett Cannon br...@python.org added the comment: I will be writing a proper task item for this (there's a reason it's a todo item =), but I will read this before writing it so feel free to leave any thoughts or ideas for the future task. -- ___

[issue10894] Making stdlib APIs private

2011-01-12 Thread SilentGhost
Changes by SilentGhost ghost@gmail.com: -- nosy: +rhettinger ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10894 ___ ___ Python-bugs-list

[issue10894] Making stdlib APIs private

2011-01-12 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: My take on this: - adding underscores to locally-defined private functions is good. +1 - -0.5 on from warnings import warn as _warn; it's useless complication, users should be able to realize warn() is a public API of the warnings module, not

[issue10894] Making stdlib APIs private

2011-01-12 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: Oh, by the way, it can be good to check that the APIs are not used too widely. Example for such a query: http://www.google.com/codesearch?q=lang%3Apython%20do_longshl=fr (in this case, it's clear that only copies of the stdlib reference that