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

Fix typos in PEP 698 (#2830)

This commit is contained in:
Mikko Korpela 2022-10-11 19:13:01 +03:00 committed by GitHub
parent 87b12e7ada
commit 67e29bf61a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
pep-0698.rst
View File

@ -334,8 +334,8 @@ insufficient for several reasons:
Runtime enforcement Runtime enforcement
------------------- -------------------
We considered having ``@typing.overrride`` enforce override safety at runtime, We considered having ``@typing.override`` enforce override safety at runtime,
similarly to how ``@overrides.overrrides`` similarly to how ``@overrides.overrides``
`does today <https://pypi.org/project/overrides/>`_. `does today <https://pypi.org/project/overrides/>`_.
We rejected this for three reasons: We rejected this for three reasons:
@ -343,7 +343,7 @@ We rejected this for three reasons:
- For users of static type checking, it is not clear this brings any benefits. - For users of static type checking, it is not clear this brings any benefits.
- There would be at least some performance overhead, leading to projects - There would be at least some performance overhead, leading to projects
importing slower with runtime enforcement. We estimate the importing slower with runtime enforcement. We estimate the
``@overrides.overrrides`` implementation takes around 100 microseconds, which ``@overrides.overrides`` implementation takes around 100 microseconds, which
is fast but could still add up to a second or more of extra initialization is fast but could still add up to a second or more of extra initialization
time in million-plus line codebases, which is exactly where we think time in million-plus line codebases, which is exactly where we think
``@typing.override`` will be most useful. ``@typing.override`` will be most useful.
@ -359,7 +359,7 @@ We rejected this for three reasons:
Marking overrides at runtime with an ``__override__`` attribute Marking overrides at runtime with an ``__override__`` attribute
--------------------------------------------------------------- ---------------------------------------------------------------
The ``@overrides.overrrides`` decorator marks methods it decorates with an The ``@overrides.overrides`` decorator marks methods it decorates with an
``__override__`` attribute. ``__override__`` attribute.
We considered having ``@typing.override`` do the same, since many typing We considered having ``@typing.override`` do the same, since many typing