+1 - I don't want Python being like Java where the only deprecation that occurs is when code is actively harmful - and it still won't be removed for backwards compatibility's sake. <div><br><div class="gmail_quote">
On Thu, Sep 10, 2009 at 4:35 PM, Brett Cannon <span dir="ltr"><<a href="mailto:brett@python.org">brett@python.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thu, Sep 10, 2009 at 15:18, Barry Warsaw <<a href="mailto:barry@python.org">barry@python.org</a>> wrote:<br>
> On Sep 10, 2009, at 6:04 PM, Antoine Pitrou wrote:<br>
><br>
>> The main reason, as I understand, is to make the big picture clearer for<br>
>> new users because there's only one advertised way to do it. While it is<br>
>> very nice for a clean sheet approach, it certainly isn't a consolation<br>
>> for people who will have to rewrite their recently broken code...<br>
><br>
> Perhaps this indicates a solution then. Let's leave getopt and optparse in<br>
> the stdlib as long as they aren't totally bitrotted into non-functionality,<br>
> or as long as there is someone willing to maintain them as the language<br>
> evolves. But let's effectively deprecate them by moving their documentation<br>
> to the backwaters so the average Python programmer will not find them, but<br>
> will find argparse instead. Once argparse is in the stdlib, all new code<br>
> should use be using it exclusively.<br>
><br>
<br>
</div>As long as they always raise a deprecation warning and it is clear<br>
they are no longer maintained then fine. Modules could be in stages<br>
of:<br>
<br>
1. pending deprecation<br>
2. deprecation<br>
3. perpetual, unmaintained bitrot (w/ docs removed; deprecation can<br>
point to last version w/ docs)<br>
4. deletion when we think no one is using it anymore (maybe next major<br>
revision of Python)<br>
<br>
And this should only apply to pure Python code as I don't want build<br>
dependency issues lying around forever. If we can make sure that the<br>
Cheeseshop gets its version updated after every micro release while it<br>
is in stage 1 or 2 this could actually work.<br>
<font color="#888888"><br>
-Brett<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
stdlib-sig mailing list<br>
<a href="mailto:stdlib-sig@python.org">stdlib-sig@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/stdlib-sig" target="_blank">http://mail.python.org/mailman/listinfo/stdlib-sig</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Jim Baker<br><a href="mailto:jbaker@zyasoft.com">jbaker@zyasoft.com</a><br>
</div>