[Python-Dev] When to remove deprecated stuff (was: Deprecating the formatter module)

[Michael Foord]

On 15 Aug 2013, at 15:40, Brett Cannon <brett at python.org> wrote:

> 
> 
> 
> On Thu, Aug 15, 2013 at 8:36 AM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> On Thu, 15 Aug 2013 08:29:35 -0400
> "R. David Murray" <rdmurray at bitdance.com> wrote:
> 
> > On Thu, 15 Aug 2013 11:22:14 +0200, Antoine Pitrou <solipsis at pitrou.net> wrote:
> > > On Thu, 15 Aug 2013 11:16:20 +0200
> > > Victor Stinner <victor.stinner at gmail.com> wrote:
> > > > 2013/8/15 Antoine Pitrou <solipsis at pitrou.net>:
> > > > > We don't have any substantial change in store for an eventual "Python
> > > > > 4", so it's quite a remote hypothesis right now.
> > > >
> > > > I prefered the transition between Linux 2 and Linux 3 (no major
> > > > change, just a "normal" release except the version), rather than the
> > > > transition between KDE 3 and KDE 4 (in short, everything was broken,
> > > > the desktop was not usable).
> > > >
> > > > I prefer to not start a list of things that we will make the
> > > > transition from Python 3 to Python 4 harder. Can't we do small changes
> > > > between each Python release, even between major versions?
> > >
> > > That's exactly what I'm saying.
> > > But some changes cannot be made without breakage, e.g. the unicode
> > > transition. Then it makes sense to bundle all breaking changes in a
> > > single version change.
> >
> > A number of us (I don't know how many) have clearly been thinking about
> > "Python 4" as the time when we remove cruft.  This will not cause any
> > backward compatibility issues for anyone who has paid heed to the
> > deprecation warnings, but will for those who haven't.
> 
> Which is why we shouldn't silence deprecation warnings.
> 
> What we should probably do is have unittest turn deprecations on by default when running your tests but leave them silent otherwise.


Hmmm.... I thought we already did this. I guess not. Anyway, I concur.

Michael

> I still think keeping them silent for the benefit of end-users is a good thing as long as we make it easier for developers to switch on warnings without thinking about it.
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk


--
http://www.voidspace.org.uk/


May you do good and not evil
May you find forgiveness for yourself and forgive others
May you share freely, never taking more than you give.
-- the sqlite blessing 
http://www.sqlite.org/different.html