On Wed, 10 Feb 2021 at 16:06, Anders Munch <ajm@flonidan.dk> wrote:

Paul Moore [mailto:p.f.moore@gmail.com]: wrote:

...

On Wed, 10 Feb 2021 at 14:33, Anders Munch <ajm@flonidan.dk> wrote:

...

The idea is to make is so that working code only needs to change once, even when supporting multiple Python versions. That one change is to add either an explicit encoding=None (for backwards-compatibility) or an explicit encoding='utf-8' (because that was intended all along). No twice about it, one change.

...

But then people who added an explicit utf-8 encoding need to remove the encoding argument again once the default value changes

Why would they do that? There's no need to remove anything. Code that doesn't use a default doesn't break because the default changes.

Because I'm against a proposal that forces *everyone* to explicitly specify the value... Your argument implies that removing the default altogether would be fine as well. Paul

On Wed, 10 Feb 2021 at 16:06, Anders Munch <ajm@flonidan.dk> wrote:

Paul Moore [mailto:p.f.moore@gmail.com]: wrote:

...

On Wed, 10 Feb 2021 at 14:33, Anders Munch <ajm@flonidan.dk> wrote:

...

The idea is to make is so that working code only needs to change once, even when supporting multiple Python versions. That one change is to add either an explicit encoding=None (for backwards-compatibility) or an explicit encoding='utf-8' (because that was intended all along). No twice about it, one change.

...

But then people who added an explicit utf-8 encoding need to remove the encoding argument again once the default value changes

Why would they do that? There's no need to remove anything. Code that doesn't use a default doesn't break because the default changes.

Because I'm against a proposal that forces *everyone* to explicitly specify the value... Your argument implies that removing the default altogether would be fine as well. Paul