> How easy would it be to search the sources and the docs for the ones that are currently public but not documented?
Comparing the docs and .c files for functions that are not documented would be fairly trivial, but it's very difficult to define something as being public if it's not documented, since that's the main definition used. If it's not in the documentation, there's not a definitive way tell that it's public (AFAIK). The presence or lack of the name starting with an underscore can sometimes be an indicator, but that's not consistently reliable. On Mon, Sep 23, 2019 at 7:59 PM MRAB <pyt...@mrabarnett.plus.com> wrote: > On 2019-09-23 21:22, Vinay Sajip via Python-Dev wrote: > > OK - but that's just one I picked at random. There are others like it - > what would be the process for deciding which ones need to be made private > and moved? Should an issue be raised to track this? > > > It's not really a question of which ones should be made private, but of > which ones should be remain public. If it's mentioned in the docs, then > it's public, otherwise it should be private. > How easy would it be to search the sources and the docs for the ones > that are currently public but not documented? > _______________________________________________ > Python-Dev mailing list -- python-dev@python.org > To unsubscribe send an email to python-dev-le...@python.org > https://mail.python.org/mailman3/lists/python-dev.python.org/ > Message archived at > https://mail.python.org/archives/list/python-dev@python.org/message/4KUPJBNXXL7VD6JPAC7YCCTD56A5OUAZ/ >
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/U3WTOSLDLIZBIB4IJPJ4LSMWQNLY7W2V/
