Steven D'Aprano wrote:
Currently it requires some extra steps or flags, which are not well known. What change are you proposing for 3.8 that will ensure that this actually gets solved? Absolutely nothing. I don't have to: we're an entire community, this doesn't have to fall only on my shoulders. I'm not even the messenger:
Because our processes don't work the way we assumed, it turns out that in practice we haven't given developers the deprecation period we thought we had. Read Nathaniel's post, if you haven't already done so: https://mail.python.org/archives/list/python-dev@python.org/message/E7QCC74O... He makes a compelling case that while we might have had the promised deprecation period by the letter of the law, in practice most developers will have never seen it, and we will be breaking the spirit of the promise if we continue with the unmodified plan. ... I'm sure that the affected devs will understand why it was their fault they couldn't see the warnings, when even people from a first-class library like SymPy took four iterations to do it right. that's Raymond. I'm just (partly) agreeing with him. Just because I don't have a solution for this problem doesn't mean the problem doesn't exist.
As the SymPy team has figured out the right pytest incantation to expose these warnings, perhaps a feature request on pytest to encapsulate that mix of options into a single flag would be a good idea?