diff options
| author | Batuhan Taskaya <batuhanosmantaskaya@gmail.com> | 2020-10-06 20:03:02 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-10-06 20:03:02 (GMT) |
| commit | 044a1048ca93d466965afc027b91a5a9eb9ce23c (patch) | |
| tree | 94ef2bca072693d83448edef4009dc840c58a3e2 /Lib/test/dataclass_module_1.py | |
| parent | bef7d299eb911086ea5a7ccf7a9da337e38a8491 (diff) | |
| download | cpython-044a1048ca93d466965afc027b91a5a9eb9ce23c.zip cpython-044a1048ca93d466965afc027b91a5a9eb9ce23c.tar.gz cpython-044a1048ca93d466965afc027b91a5a9eb9ce23c.tar.bz2 | |
bpo-38605: Make 'from __future__ import annotations' the default (GH-20434)
The hard part was making all the tests pass; there are some subtle issues here, because apparently the future import wasn't tested very thoroughly in previous Python versions.
For example, `inspect.signature()` returned type objects normally (except for forward references), but strings with the future import. We changed it to try and return type objects by calling `typing.get_type_hints()`, but fall back on returning strings if that function fails (which it may do if there are future references in the annotations that require passing in a specific namespace to resolve).
Diffstat (limited to 'Lib/test/dataclass_module_1.py')
| -rw-r--r-- | Lib/test/dataclass_module_1.py | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/Lib/test/dataclass_module_1.py b/Lib/test/dataclass_module_1.py index 87a33f8..9f0aeda 100644 --- a/Lib/test/dataclass_module_1.py +++ b/Lib/test/dataclass_module_1.py @@ -1,9 +1,3 @@ -#from __future__ import annotations -USING_STRINGS = False - -# dataclass_module_1.py and dataclass_module_1_str.py are identical -# except only the latter uses string annotations. - import dataclasses import typing |