It seems evident that the problems with PEP 563 have been well-known at least to pydantic for several years, as you can see in the issue Samuel Colvin linked: https://github.com/samuelcolvin/pydantic/issues/2678

That said, while I do think that "please contact upstream when you see a problem developing, not just before a major deadline" is a good lesson to take away from this, it is probably not worth litigating the question of the particular manner of the notification. As much as I think it would have been good for this discussion to happen 6 months, 1 year, 2 years or 3 years ago, "before the code freeze" is a heck of a lot better than "after the release" (which is often when the notification comes in, and why we have been encouraging people to test against alphas and betas).

Hopefully we can let it rest by saying that the timing of learning about this apparently urgent situation could have been much better, but it could have been worse as well.

Best,
Paul

On 4/15/21 7:12 PM, Christopher Barker wrote:
On Thu, Apr 15, 2021 at 3:29 PM Bernat Gabor <gaborjbernat@gmail.com> wrote:
> I'm a bit surprised that this topic is brought up just days before the feature freeze of Python 3.10.

I have not idea about the technical details, but I think there is a bit of a discomment in the community:

Annotations have been around for years.

More recently, there was an official specification of how to use them for type hinting (was that PEP 484? a bit confused as that appears to still be provisional -- but anyway)

Since the specification for type hinting, a lot of work has been done on/with static type checkers (e.g. MyPy).

That work has informed the changes / improvements / proposals to the annotation and type system in Python.

However, those of us that are not actively involved (and maybe not that interested) in static typing have been not paying a great deal of attention to those efforts.

But some of us may, in fact, be using annotations for other reasons, but since we haven't been involved in the discussion, some issues may have been missed.

-CHB


--
Christopher Barker, PhD (Chris)

Python Language Consulting
  - Teaching
  - Scientific Software Development
  - Desktop GUI and Web Development
  - wxPython, numpy, scipy, Cython

_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-leave@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/5TGKKRZXGQROQKS2WX6WFGCHTMNUJYBF/
Code of Conduct: http://python.org/psf/codeofconduct/