Just add the appropriate code to filter that category of warnings. I think you have the option of two lines of Python code or one environment variable.
I can assure you that many users will not know how to do either of those things.
Eric
On Mon, Feb 24, 2020 at 11:16 PM David Mertz <mertz@gnosis.cx> wrote:
On Mon, Feb 24, 2020 at 4:08 PM Alex Hall <alex.mojaki@gmail.com> wrote:
--Even when there is a wealth of code out there that will become broken
by this change?
Not broken, just noisy.
Noisy *IS* broken!
In some ways it's one of the worst kinds of broken. Working with libraries that import other libraries and trigger warnings that have nothing to do with MY code is super annoying. I know this is a thorny question, since too-quiet means things don't change, and too noisy means users get warnings they are helpless to deal with.
Keeping medicines from the bloodstreams of the sick; food
from the bellies of the hungry; books from the hands of the
uneducated; technology from the underdeveloped; and putting
advocates of freedom in prisons. Intellectual property is
to the 21st century what the slave trade was to the 16th.
_______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-leave@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/3CMQ6ZMBRV35URI36DXSZWYPAST6TZTS/ Code of Conduct: http://python.org/psf/codeofconduct/