Showing content from http://mail.python.org/pipermail/python-dev/attachments/20150912/0e9cdc1d/attachment.html below:
<p dir="ltr">Someone else brought up warnings in Python 2.7 and my response was that you already get the warning in Python 3 so why get it twice across different versions?</p>
<br><div class="gmail_quote"><div dir="ltr">On Fri, Sep 11, 2015, 22:48Â Serhiy Storchaka <<a href="mailto:storchaka@gmail.com">storchaka@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 08.09.15 19:59, Brett Cannon wrote:<br>
> The approaches to module deprecation I have seen are:<br>
> 1. Nothing changes to the deprecation process; you deprecate a module<br>
> and remove it in one to two releases<br>
> 2. Deprecate the module but with no plans for removal until Python 2.7<br>
> reaches its EOL (I have been calling this Python 4)<br>
> 3. Document the deprecation but no actual code deprecation<br>
<br>
Of course #2 LGTM. What if at the same time add Py3k warning in next 2.7<br>
bugfix release?<br>
<br>
<br>
_______________________________________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org" target="_blank">Python-Dev@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/python-dev" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="https://mail.python.org/mailman/options/python-dev/brett%40python.org" rel="noreferrer" target="_blank">https://mail.python.org/mailman/options/python-dev/brett%40python.org</a><br>
</blockquote></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4