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

2010-11-08 Thread Ron Adam
On 11/08/2010 10:26 PM, Nick Coghlan wrote: On Tue, Nov 9, 2010 at 11:18 AM, Ron Adam 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 uncha

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

2010-11-08 Thread Nick Coghlan
On Tue, Nov 9, 2010 at 11:18 AM, Ron Adam 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 > ch

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

2010-11-08 Thread Ron Adam
On 11/08/2010 05:44 AM, Nick Coghlan wrote: All, I was about to commit the patch for issue 2001 (the improvements to the pydoc web server and the removal of the Tk GUI) when I realised that pydoc.serve() and pydoc.gui() are technically public standard library APIs (albeit undocumented ones).

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

2010-11-08 Thread Ron Adam
On 11/08/2010 09:12 AM, exar...@twistedmatrix.com wrote: On 11:44 am, ncogh...@gmail.com wrote: All, I was about to commit the patch for issue 2001 (the improvements to the pydoc web server and the removal of the Tk GUI) when I realised that pydoc.serve() and pydoc.gui() are technically publi

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

2010-11-08 Thread R. David Murray
On Mon, 08 Nov 2010 17:02:24 +0100, wrote: > If there is no enormous difficulty in maintaining compatibility, I think > the usual deprecation process should be followed. We don’t know who is > using pydoc as a library, so let’s play safe and not risk breaking their > code (especially consider

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

2010-11-08 Thread Georg Brandl
Am 08.11.2010 17:02, schrieb Éric Araujo: > Hi Nick, > > If there is no enormous difficulty in maintaining compatibility, I think > the usual deprecation process should be followed. We don’t know who is > using pydoc as a library, so let’s play safe and not risk breaking their > code (especially

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

2010-11-08 Thread Éric Araujo
Hi Nick, If there is no enormous difficulty in maintaining compatibility, I think the usual deprecation process should be followed. We don’t know who is using pydoc as a library, so let’s play safe and not risk breaking their code (especially considering that it must not have been easy to write c

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

2010-11-08 Thread exarkun
On 11:44 am, ncogh...@gmail.com wrote: All, I was about to commit the patch for issue 2001 (the improvements to the pydoc web server and the removal of the Tk GUI) when I realised that pydoc.serve() and pydoc.gui() are technically public standard library APIs (albeit undocumented ones). Current

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

2010-11-08 Thread Nick Coghlan
All, I was about to commit the patch for issue 2001 (the improvements to the pydoc web server and the removal of the Tk GUI) when I realised that pydoc.serve() and pydoc.gui() are technically public standard library APIs (albeit undocumented ones). Currently the patch switches serve() to start th