On Wed, Nov 17, 2010 at 8:30 AM, Nick Coghlan <ncogh...@gmail.com> wrote: > The library documentation is *not* the right place for quibbling about > what constitutes a public API when using other means than the library > documentation to find APIs to call.
Quibbling can happen on the mailing list, where it can be ignored by those who aren't interested. But the documentation is the right place to document what we come up with for the standard library. I expect what the tools do will inform any decisions, and the tools (those in the stdlib) will henceforth be maintained with that in mind. I *am* suggesting that the scope of this be restricted to what's appropriate for the standard library, rather than a general recommendation for others. Third-party projects are free to use what we come up with, or provide their own policies. That's theirs to decide, and I see no value in interfering with that. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org> "A storm broke loose in my mind." --Albert Einstein _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
