[Python-Dev] Backward incompatible API changes in the pydoc module

Tue Nov 9 05:26:22 CET 2010

On Tue, Nov 9, 2010 at 11:18 AM, Ron Adam <rrr at ronadam.com> wrote:
> What do you think about adding a new _pydoc3.py module along with a
> pydoc3.py loader module with a basic user api.  The number 3, so that it
> match's python3.x.
>> We can then keep the old pydoc.py unchanged and be free to make a lot more
> changes to the _pydoc3.py file without having to be even a little paranoid.

I think changing the behaviour of the pydoc command line app is a fine
idea - it's only the pydoc.serve and pydoc.gui functions that are
worrying me. As I noted on the tracker issue, there's a reasonably
clean way to do this, even given the coupling between the 3.1 GUI app
and server: leave the existing serve() and gui() functions alone
(aside from adding DeprecationWarning), and add your new
implementation as a parallel private API.
Cheers,
Nick.
-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia