People distribute code via pypi. if we reject uploads of packages with these problems and link to fixers (modernize can be taught what to do), we prevent them from spreading further. A few years after doing that, we can revisit how much pain and for whom making this a SyntaxWarning or even SyntaxError would actually be.

it isn't useful to tell users of packages to spend time figuring out who to complain to that some packages code that they somehow depend on (often transitively) is not modern enough.

On Tue, Aug 6, 2019 at 5:39 PM Rob Cliffe via Python-Dev <python-dev@python.org> wrote:

On 07/08/2019 01:14:08, Chris Angelico wrote:
> On Wed, Aug 7, 2019 at 10:03 AM Steven D'Aprano <steve@pearwood.info> wrote:
>> - Keep the SyntaxWarning silent by default for 3.8. That gives us
>> another year or more to gently pressure third-party libraries to fix
>> their code, and to find ways to encourage developers to run with
>> warnings enabled.
> How do you propose to apply this pressure?
>
> How about: whenever a third-party library uses a potentially-wrong
> escape sequence, it creates a message on the console. Then when
> someone sees that message, they can post a bug report against the
> package.
>
> In other words, a non-silent warning.
>
> ChrisA
> _______________________________________________
>
The interpreter knows which module contains the questionable string.
So: is it feasible for the warning message to include something like
"... If you are not the maintainer of xxxmodule.py, please contact
them, or post a bug report on ..."
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-leave@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/JJULDRHOTETV2LDLJE6RWKZ6HCCPHTUP/