On Thu, Jan 27, 2022 at 10:47 AM Steven D'Aprano <st...@pearwood.info>
wrote:

> > >Getting the right people to pay attention to them is always the hard
> part.
>
> Or maybe, as a developer (not an end-user of an app), you could be more
> proactive in reporting those warnings to the third party, and
> encouraging them to fix them. Maybe even submitting a patch?
>

Personally, I do exactly that -- but more often than not (thankfully) the
upstream project is already working on it, or already fixed it, but in a
version that I can't use yet. So then I really want to silence those
warnings. Which is pretty easy to do with pytest, but maybe not so easy
everywhere?


>  But we shouldn't just
> dismiss warnings in those dependencies as "warnings I don't care about"
> and ignore them as Not My Problem.
>

Unless we have done due diligence already :-)

-CHB


-- 
Christopher Barker, PhD (Chris)

Python Language Consulting
  - Teaching
  - Scientific Software Development
  - Desktop GUI and Web Development
  - wxPython, numpy, scipy, Cython
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/YUWICC2Q274FBOZF5BX2N3BYEO7MHMQH/
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to