On Thu, Oct 17, 2013 at 09:59:58AM -0400, Donald Stufft wrote: > On Oct 17, 2013, at 9:53 AM, Nick Coghlan <ncogh...@gmail.com> wrote: > > Yes, but breaking these users' uploads is not the way to do that. > > That's an incredibly user hostile step to take, and the problem > > doesn't even come close to justifying breaking even a > > not-really-working process (since you can work around the current > > breakage by manually installing the dependencies - you can't work > > around an inability to upload without making changes to your code). > > > > If you really wanted to push them towards fixing their releases, you > > could always have PyPI send them an email saying something like: > ... > > This could be part of the deprecation process, but unless there's a plan > in place to deprecate them I don't know how useful this email would be. > It's a reactive warning to something that confuses people while they are > creating a package. In other words by the time the email goes out they've > already been confused.
Is it possible to make 'python setup.py sdist upload' emit a warning message about using these deprecated fields, without rejecting the upload? Marius Gedminas -- Q: How many IBM CPU's does it take to execute a job? A: Four; three to hold it down, and one to rip its head off.
signature.asc
Description: Digital signature
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
