VimPlug/typeshed
1
0
Fork 0
mirror of https://github.com/davidhalter/typeshed.git synced 2026-05-06 21:43:59 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Style and formatting docs fixes (#15299)

Browse Source 
* Add PEP links for more context
* Normalize the virtualenv name from `.venv3` to `.venv` (the [documentation suggests](https://github.com/python/typeshed/blob/main/CONTRIBUTING.md#-or-create-a-local-development-environment) creating a `.venv` name, not `.venv3`so `venv3` is not used anywhere else)
This commit is contained in:
Semyon Moroz
2026-01-18 08:49:20 +00:00
committed by GitHub
parent b94c9e8e48
commit d2154f5ad8
3 changed files with 27 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tests/REGRESSION.md
+3 -2
View File
@@ -99,8 +99,9 @@ rather than `.pyi` files)
is that the test cases cannot always use modern syntax for type hints.
While we can use `from __future__ import annotations` to enable the use of
modern typing syntax wherever possible,
type checkers may (correctly) emit errors if PEP 604 syntax or PEP 585 syntax
is used in a runtime context on lower versions of Python. For example:
type checkers may (correctly) emit errors if [PEP 604](https://peps.python.org/pep-0604/)
syntax or [PEP 585](https://peps.python.org/pep-0585/) syntax is used
in a runtime context on lower versions of Python. For example:
```python
from __future__ import annotations