This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ezio.melotti
Recipients Ramchandra Apte, alex, asvetlov, christian.heimes, docs@python, ezio.melotti, giampaolo.rodola, hynek, jab, pitrou, r.david.murray, rhettinger, vstinner, yating.huang
Date 2016-01-01.03:24:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1451618657.96.0.304750754668.issue17006@psf.upfronthosting.co.za>
In-reply-to
Content
> People are going to skip warning boxes if they occur too often.

I'm not sure I agree.  This would be true if they were abused for trivial things ("Warnings: using .pop() on a empty list will return an IndexError!"), but I don't think they are.

I think warnings are ignored only by people that are already familiar with the module and its limitation/issues, and that know what they are doing.  If the warning is not evident, people are going to miss it [0].

If warnings are used correctly, people will spot them easily and read them (or ignore them if they already know what they are warning against).

[0]: I know I missed it in e.g. https://api.jquery.com/die/ -- the function is deprecated, but (currently) this is only written in the top right corner and in small in the category at the top -- two places that are easily overlooked.  https://api.jquery.com/toggle-event/ on the other hand has a clearly visible yellow box at the top that immediately says that the method is deprecated.
History
Date User Action Args
2016-01-01 03:24:18ezio.melottisetrecipients: + ezio.melotti, rhettinger, pitrou, vstinner, giampaolo.rodola, christian.heimes, alex, r.david.murray, jab, asvetlov, docs@python, Ramchandra Apte, hynek, yating.huang
2016-01-01 03:24:17ezio.melottisetmessageid: <1451618657.96.0.304750754668.issue17006@psf.upfronthosting.co.za>
2016-01-01 03:24:17ezio.melottilinkissue17006 messages
2016-01-01 03:24:16ezio.melotticreate