On 11/08/2010 10:26 PM, Nick Coghlan wrote:
On Tue, Nov 9, 2010 at 11:18 AM, Ron Adam<r...@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.
Ok, I guess that's what needs to be done then. I can try to do it over the
next few days, and will probably need a bit more advise on how to add in
the depreciation warnings. Or if you want to go ahead and do it, I'm more
than OK with that.
Thanks for the help on this. I do appreciate it.
Cheers,
Ron
_______________________________________________
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
