On Fri, Jan 29, 2010 at 17:37, Ezio Melotti <ezio.melo...@gmail.com> wrote: > On 28/01/2010 8.39, Brett Cannon wrote: >> >> On Wed, Jan 27, 2010 at 15:54, Ezio Melotti<ezio.melo...@gmail.com> >> wrote: >>> >>> I noticed that in the py3k doc 'mktemp' is marked as deprecated since >>> Python >>> 2.3 [1], but the function is still there and doesn't raise any warning. >>> Looking at the source I found out that there is a warning, but it is >>> commented out [2], the reason being because they are "too annoying". >>> There was already a discussion about this on python-dev [3], but now that >>> the DeprecationWarnings are silenced by default [4] the warning could be >>> restored. >>> If the comment can be removed I will fix it in trunk/py3k and possibly in >>> 2.6/3.1 too, if #7319 will be backported. >>> (Brett, are you planning to backport it?) >> >> If you mean forward-port to Python 3.1, then yes I am planning to >> merge it. Since Python 3.2 is not due out for nearly a year I wanted >> to wait a little while to make sure that the wording in the warnings >> docs made sense. But if you and others want to start actively turning >> some warnings on that will simply be too annoying when running the >> test suite I can do it sooner rather than later. >> >> -Brett > > I mean port it to py3k first and then backport it from trunk to 2.6 and > from py3k to 3.1.
I am only porting from trunk to py3k. Since this is not backwards-compatible I am not backporting to 2.6 or 3.1. > If you want to wait then it's probably enough to add a > note to the ticket and I'll fix it later. Make sure to mark it as dependent on issue 7319 which I am using to track the fact I still need to port it. -Brett _______________________________________________ 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
