Fix a typo in code style documentation (#15877)

Fix typo in documentation file
This commit is contained in:
UncertainBadg3r 2023-07-27 17:17:28 -04:00 committed by GitHub
parent cb4bade2fe
commit 146dc8fc20
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -271,7 +271,7 @@ While tests are still critical to confirm that the proper _values_ are created,
Our goal is to reach complete hinting coverage on all code with relatively strict mypy configuration. Our goal is to reach complete hinting coverage on all code with relatively strict mypy configuration.
This provides a rigorous level of checking for basic errors such as accessible unavailable attributes, mixing different types of elements in lists, treating a list as if it is a dict, and so on. This provides a rigorous level of checking for basic errors such as accessible unavailable attributes, mixing different types of elements in lists, treating a list as if it is a dict, and so on.
Note that as of Python 3.9 there were some broad changes implemented that allowed for hinting with the builting `list[int]` as opposed to `typing.List[int]`. Note that as of Python 3.9 there were some broad changes implemented that allowed for hinting with the builtin `list[int]` as opposed to `typing.List[int]`.
Also, in new Python versions `Union[str, int]` can be written as `str | int`. Also, in new Python versions `Union[str, int]` can be written as `str | int`.
While it is possible to some degree for us to use those forms despite running in older Python versions, we will not presently be using the newer forms. While it is possible to some degree for us to use those forms despite running in older Python versions, we will not presently be using the newer forms.