Jean-Paul Calderone <exar...@divmod.com> writes: > Hm. But docutils isn't part of the standard library, and the > documentation refers to it.
Fair enough, because the documentation is generated using Docutils. > And the docs link to ActivePython and Enthought's Python distribution. I consider those to be exceptions that prove the rule: they are “standard Python” in a different form. > And they link to things like "Collin Winter’s functional module" and > Django and PyOpenGL and so forth. I don't know enough about those to comment. > I don't think anyone would seriously suggest removing all references to > third-party software from the Python documentation. No, and nor did I. I'm suggesting that *adding* such a reference has a high barrier. > Perhaps the criterion that David is looking to have is explained is > that people would probably prefer for his app to get a bit more > popular before Python itself starts pointing people in its direction. Right. The process is usually in the following order: * get the code registered on PyPI * get a community of users and make the code meet their needs well * discuss adding some or all of the code to Python, by (in recent years) raising the topic on ‘python-ideas’ * defend the proposal against all comers to ensure it's actually a good idea * await further instructions -- \ “It seems intuitively obvious to me, which means that it might | `\ be wrong.” —Chris Torek | _o__) | Ben Finney _______________________________________________ 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
