Re: [Python-Dev] Soliciting comments on the future of the cmdmodule (bpo-33233)

On Sat, Apr 07, 2018 at 06:53:44PM +, Brett Cannon wrote: > > Raymond has stated that he is happy to work on it if there are any bugs > > reported on it, and if he's not available, I'm sure somebody will. > > Actually Raymond said he *teaches* the module, not that he wanted to > maintain it.

Re: [Python-Dev] Soliciting comments on the future of the cmdmodule (bpo-33233)

On Sat, 7 Apr 2018 at 02:09 Steven D'Aprano wrote: > On Sat, Apr 07, 2018 at 09:30:05AM +0100, Paul Moore wrote: > > On 7 April 2018 at 04:13, Steve Dower wrote: > > > Better to deprecate it before it becomes broken, in my opinion. > > That argument

Re: [Python-Dev] Soliciting comments on the future of the cmdmodule (bpo-33233)

On Sat, Apr 07, 2018 at 09:30:05AM +0100, Paul Moore wrote: > On 7 April 2018 at 04:13, Steve Dower wrote: > > Better to deprecate it before it becomes broken, in my opinion. That argument could be applied to everything in the std lib. > > Having someone willing and

Re: [Python-Dev] Soliciting comments on the future of the cmdmodule (bpo-33233)

On 7 April 2018 at 04:13, Steve Dower wrote: > Better to deprecate it before it becomes broken, in my opinion. > > Having someone willing and able to review and merge changes is the best > criteria for whether a module is still supported or not. I think there's a

Re: [Python-Dev] Soliciting comments on the future of the cmdmodule (bpo-33233)

Better to deprecate it before it becomes broken, in my opinion. Having someone willing and able to review and merge changes is the best criteria for whether a module is still supported or not. Top-posted from my Windows phone From: Raymond Hettinger Sent: Friday, April 6, 2018 18:55 To: Ned