On Fri, Apr 10, 2009 at 9:40 AM, Tarek Ziadé <span dir="ltr"><<a href="mailto:ziade.tarek@gmail.com">ziade.tarek@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">> Why change the name? A different name isn't going to be better enough to be<br>
> worth the hassle. Deprecation is waaaay overrated as a tool for reducing the<br>
> pain of making people change their code or habits.<br>
<br>
</div></div>I don't think it's a good idea to have a different name in PKG-INFO<br>
and in the arguments to describe<br>
the same element. we should have the same name everywhere for<br>
consistency at the end.<br>
<br>
I don't see anything wrong about adding a simple deprecation warning<br>
here, It won't happen again<br>
for quite a while.<br>
</blockquote><div><br>People who install packages freak out over warnings. If you could do a warning during a PyPI upload, then someone who can actually make a change might see it. People installing a package should not see this warning. I feel very strongly about this as a general rule - putting messages intended for packagers into the output presented during installation is distracting and disconcerting and useless.<br>
<br>In the "check" command it would be entirely proper to issue a warning. But no one is going to re-release a project just to fix the spelling of this argument in setup.py, and a lot of libraries just don't get updated often, or people deliberately use old versions to avoid regression. So outside of the check command it should not cause any warning.<br>
</div></div><br>-- <br>Ian Bicking | <a href="http://blog.ianbicking.org">http://blog.ianbicking.org</a><br>