On Sat, Apr 11, 2009 at 3:33 PM, Tarek Ziadé <[email protected]> wrote:
>>> I don't see anything wrong about adding a simple deprecation warning >>> here, It won't happen again >>> for quite a while. >> >> 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. >> >> 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. > > Right, sounds like oups, send it too early Right, sounds like a good practice. So what shall we do for install_requires ? I'd be in favor of : - keeping the new PKG-INFO Tres proposed - maintaining both setup() arguments (like license and licence) - documenting the new argument - adding the warning in the 'check' command Cheers Tarek _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
