iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 597: Fix rest format. (#1858)

This commit is contained in:
Inada Naoki 2021-03-03 12:22:59 +09:00 committed by GitHub
parent 5a4ada6b84
commit b95c727b3e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
pep-0597.rst
View File

@ -277,23 +277,23 @@ https://mail.python.org/archives/list/python-dev@python.org/thread/SFYUP2TWD5JZ5
* Why not implement this in linters? * Why not implement this in linters?
* ``encoding="locale"`` and ``io.text_encoding()`` must be in * ``encoding="locale"`` and ``io.text_encoding()`` must be in
Python. Python.
* It is difficult to find all caller of functions wrapping * It is difficult to find all caller of functions wrapping
``open()`` or ``TextIOWrapper()``. (See ``io.text_encoding()`` ``open()`` or ``TextIOWrapper()``. (See ``io.text_encoding()``
section.) section.)
* Many developers will not use the option. * Many developers will not use the option.
* Some developers use the option and report the warnings to * Some developers use the option and report the warnings to
libraries they use. So the option is worth enough even though libraries they use. So the option is worth enough even though
many developers won't use it. many developers won't use it.
* For example, I find [7]_ and [8]_ by running * For example, I find [7]_ and [8]_ by running
``pip install -U pip`` and find [9]_ by running ``tox`` ``pip install -U pip`` and find [9]_ by running ``tox``
with the reference implementation. It demonstrates how this with the reference implementation. It demonstrates how this
option can be used to find potential issues. option can be used to find potential issues.
References References