[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Change by Jakub Wilk : -- nosy: +jwilk ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Change by Eryk Sun : -- Removed message: https://bugs.python.org/msg405693 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Change by Eryk Sun : -- nosy: +AlexWaygood, Anthony Sottile, BTaskaya, barry, brett.cannon, eric.smith, gousaiyang, gvanrossum, levkivskyi, lukasz.langa, methane, miss-islington, pablogsal, serhiy.storchaka, steven.daprano, terry.reedy, veky -ahmedsayeed1982, ezio.melotti, vstinner

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Ahmed Sayeed added the comment: With this patch (not sure yet whether it's relevant) in place: ... http://www-look-4.com/category/computers/ diff --git a/gdb/testsuite/lib/gdbserver-support.exp b/gdb/testsuite/lib/gdbserver-support. Exp https://komiya-dental.com/health/healthy-foods/ index

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Change by Alex Waygood : -- nosy: +AlexWaygood ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Serhiy Storchaka added the comment: I think it would help if we could enable some future feature globally by command line option or environment variable, without modifying all source files. It would allow users to quickly test their code base for compatibility with future changes. The

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Steven D'Aprano added the comment: Now that we're in 3.11, people are starting to notice that stringy annotations are not the default (see #45499 for example). What can we do to get PEP 649 moving forward? -- nosy: +steven.daprano ___ Python

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Batuhan Taskaya added the comment: > May I ask, is this going forward? I installed 3.11-dev, it's not there > (though __future__ claims it should be). I understand if it isn't done yet, > just want to know if there's risk it will be postponed again (or even given > up). We are still

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Vedran Čačić added the comment: May I ask, is this going forward? I installed 3.11-dev, it's not there (though __future__ claims it should be). I understand if it isn't done yet, just want to know if there's risk it will be postponed again (or even given up). -- nosy: +veky

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

miss-islington added the comment: New changeset f84f1b5c638eeb6e13c287fe5ebf3a7d2fdb60e9 by Saiyang Gou in branch 'master': bpo-38605: Update __future__ module doc as `annotations` is now "mandatory in 3.11" (GH-25602)

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Change by Saiyang Gou : -- pull_requests: +24318 pull_request: https://github.com/python/cpython/pull/25602 ___ Python tracker ___

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Change by Anthony Sottile : -- nosy: +Anthony Sottile nosy_count: 14.0 -> 15.0 pull_requests: +24316 stage: resolved -> patch review pull_request: https://github.com/python/cpython/pull/25596 ___ Python tracker

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Guido van Rossum added the comment: I don't like adding a flag. In the PEP-563-by-default world we didn't need a flag. Perhaps once Larry implements inspect.get_annotations() (issue43817) we can make inspect.signature() always call that? -- ___

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Batuhan Taskaya added the comment: > Hopefully Batuhan has a recollection of what I am thinking of, there was some > significant delay while we figured out what to do about some of these. The major one that I'd recall is that inspect.signature() just uses whatever is in __annotations__

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Guido van Rossum added the comment: I haven't followed this precisely, but I recall that when we first made PEP 563 the default, we had to fix a number of bugs in various library modules (e.g. inspect) that were only apparent when `from __future__ import annotations` was used. I hope we're

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

STINNER Victor added the comment: > New changeset b0544ba77cf86074fb1adde00558c67ca75eeea1 by Pablo Galindo in > branch 'master': Copy of the NEWS entry: Revert making ``from __future__ import annotations`` the default. This follows the Steering Council decision to postpone PEP 563 changes

[issue38605] [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11

Change by STINNER Victor : -- title: [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.10 -> [typing] PEP 563: Postponed evaluation of annotations: enable it by default in Python 3.11 ___ Python tracker