Re: [Python-Dev] When to remove deprecated stuff

2013-08-22 Thread Petri Lehtinen
R. David Murray wrote: > > So you're still using features deprecated three releases ago, you haven't > > checked for DeprecationWarnings and it's Django making your life difficult? > > > > Why not check for the deprecation warnings? > > Doing so makes very little difference. > > This is my opin

Re: [Python-Dev] When to remove deprecated stuff

2013-08-22 Thread Stephen J. Turnbull
R. David Murray writes: > It is the *change itself* that causes > action to be needed. If a project has a policy of dealing with deprecated > features when the warnings happen, then they need to do that work before > the version where the feature is removed is released. If they have > a pol

[Python-Dev] PEP 446 (make FD non inheritable) ready for a final review

2013-08-22 Thread Victor Stinner
Hi, I know that I wrote it more than once, but I consider that my PEP 446 is now ready for a final review: http://www.python.org/dev/peps/pep-0446/ The implementation is also working, complete and ready for a review. http://hg.python.org/features/pep-446 http://bugs.python.org/issue18571 I run

Re: [Python-Dev] When to remove deprecated stuff

2013-08-22 Thread R. David Murray
On Thu, 22 Aug 2013 20:00:14 +0200, Ezio Melotti wrote: > On Thu, Aug 22, 2013 at 4:43 PM, R. David Murray > wrote: > > On Thu, 22 Aug 2013 16:45:29 +0300, Michael Foord > > wrote: > >> > >> On 22 Aug 2013, at 14:00, Petri Lehtinen wrote: > >> > > >> > Django's deprecation policy works like t

Re: [Python-Dev] When to remove deprecated stuff

2013-08-22 Thread Ezio Melotti
On Thu, Aug 22, 2013 at 7:45 PM, Donald Stufft wrote: > > On Aug 22, 2013, at 1:34 PM, Ezio Melotti wrote: > >> Hi, >> >> On Thu, Aug 22, 2013 at 1:00 PM, Petri Lehtinen wrote: >>> >>> Removing some cruft on each release can be very painful for users. >>> >>> Django's deprecation policy works li

Re: [Python-Dev] When to remove deprecated stuff

2013-08-22 Thread Ezio Melotti
On Thu, Aug 22, 2013 at 4:43 PM, R. David Murray wrote: > On Thu, 22 Aug 2013 16:45:29 +0300, Michael Foord > wrote: >> >> On 22 Aug 2013, at 14:00, Petri Lehtinen wrote: >> > >> > Django's deprecation policy works like this: They deprecate something >> > in version A.B. It still works normally

Re: [Python-Dev] When to remove deprecated stuff

2013-08-22 Thread Donald Stufft
On Aug 22, 2013, at 1:34 PM, Ezio Melotti wrote: > Hi, > > On Thu, Aug 22, 2013 at 1:00 PM, Petri Lehtinen wrote: >> >> Removing some cruft on each release can be very painful for users. >> >> Django's deprecation policy works like this: They deprecate something >> in version A.B. It still w

Re: [Python-Dev] When to remove deprecated stuff

2013-08-22 Thread Ezio Melotti
Hi, On Thu, Aug 22, 2013 at 1:00 PM, Petri Lehtinen wrote: > > Removing some cruft on each release can be very painful for users. > > Django's deprecation policy works like this: They deprecate something > in version A.B. It still works normally in A.B+1, generates a > (silenced) DeprecationWarni

Re: [Python-Dev] When to remove deprecated stuff

2013-08-22 Thread Chris Angelico
On Thu, Aug 22, 2013 at 11:45 PM, Michael Foord wrote: > On 22 Aug 2013, at 14:00, Petri Lehtinen wrote: >> Django's deprecation policy works like this: They deprecate something >> in version A.B. It still works normally in A.B+1, generates a >> (silenced) DeprecationWarning in A.B+2, and is fina

Re: [Python-Dev] When to remove deprecated stuff

2013-08-22 Thread R. David Murray
On Thu, 22 Aug 2013 16:45:29 +0300, Michael Foord wrote: > > On 22 Aug 2013, at 14:00, Petri Lehtinen wrote: > > > Terry Reedy wrote: > >> On 8/15/2013 8:29 AM, R. David Murray wrote: > >> > >>> A number of us (I don't know how many) have clearly been thinking about > >>> "Python 4" as the ti

Re: [Python-Dev] cpython: Cleanup test_builtin

2013-08-22 Thread Serhiy Storchaka
22.08.13 14:48, Victor Stinner написав(ла): You forgot self.addCleanup(unlink, TESTFN) (here and in other places). These functions call write_testfile() which creates the file but also schedules its removal when the test is done (since my changeset): def write_testfile(self): # N

Re: [Python-Dev] When to remove deprecated stuff

2013-08-22 Thread Antoine Pitrou
Le Thu, 22 Aug 2013 14:00:06 +0300, Petri Lehtinen a écrit : > Terry Reedy wrote: > > On 8/15/2013 8:29 AM, R. David Murray wrote: > > > > >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 backw

Re: [Python-Dev] cpython: Cleanup test_builtin

2013-08-22 Thread Victor Stinner
> You forgot self.addCleanup(unlink, TESTFN) (here and in other places). These functions call write_testfile() which creates the file but also schedules its removal when the test is done (since my changeset): def write_testfile(self): # NB the first 4 lines are also used to test input

Re: [Python-Dev] When to remove deprecated stuff

2013-08-22 Thread Petri Lehtinen
Terry Reedy wrote: > On 8/15/2013 8:29 AM, R. David Murray wrote: > > >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 > >deprecatio

Re: [Python-Dev] cpython: Cleanup test_builtin

2013-08-22 Thread Serhiy Storchaka
22.08.13 02:59, victor.stinner написав(ла): http://hg.python.org/cpython/rev/0a1e1b929665 changeset: 85308:0a1e1b929665 user:Victor Stinner date:Thu Aug 22 01:58:12 2013 +0200 summary: Cleanup test_builtin files: Lib/test/test_builtin.py | 16 1 files