<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><blockquote type="cite"><font class="Apple-style-span" color="#000000"><br></font><div class="gmail_quote">On Tue, Mar 2, 2010 at 15:55, Florent Xicluna <span dir="ltr"><<a href="mailto:florent.xicluna@gmail.com">florent.xicluna@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto; ">
Hello,<br>
<br>
I would like to open a discussion on the meaning of deprecation warnings in 2.7.<br>
I assume, but I may be wrong, that 2.7 will be the last version in the 2.x<br>
branch. With this assumption, we should not find many things deprecated in 2.7<br>
final.<br>
<br>
On the other hand, the list of py3k deprecation warnings is increasing a lot.<br>
And more users will probably start to move from 2.7 to the 3.1 release.<br>
<br>
While working on ticket #7092 and #7849, we started to discuss some proposals<br>
to simplify the deprecation warnings for 2.7.<br>
<br>
We discussed these 2 proposals:<br>
<br>
1) in 2.6 there's no distinction between py3k and normal deprecations: they<br>
share the same category, DeprecationWarning. The "-3" switch enables the<br>
py3k DeprecationWarning and SyntaxWarning.<br>
Do we need to introduce a subclass Py3kDeprecationWarning in 2.7? It will<br>
make it easier to separate both kinds of deprecations (2.x and 3.x), and<br>
to filter them.<br>
<br>
2) a different idea is to deprecate the "-3" switch and consider all py3k<br>
deprecations as normal deprecations. <br></blockquote></div></blockquote><div><br></div><div>-1 for several reasons. </div><div><br></div><div>1) We've advertised -3 as part of TheOneTrueWay(tm). It's a core part of our transition story, so we should keep that as clean/consistent as possible. Deprecating the -3 switch seems like shooting ourselves in the foot.</div><div><br></div><div>2) There is some chance that there will be a 2.8, so it isn't helpful to burn down our bridges.</div><div><br></div><div>ISTM, nothing is currently broken and in need of "fixing" in 2.7.</div><div>I don't see any advantage to conflating py3k warnings with other deprecations.</div><div><br></div><div><br></div><div>Raymond</div></div></body></html>