Sounds good to me. I can make the docs and `typing_extensions` changes. Should it also be added into `typing` immediately?
Are there any other `foo_default` parameters that anyone thinks should be added while we’re at it? There was a brief discussion about `init_default` [1] a while back, but the user didn’t seem committed to the idea.
-Erik
[1] https://github.com/microsoft/pylance-release/issues/2494#issuecomment-107412...
From: Shantanu Jain
Sent: Wednesday, November 30, 2022 11:10 PM
To: Eric Traut
Cc: typing-sig@python.org
Subject: [Typing-sig] Re: Could we add frozen_default to "PEP 681 – Data Class Transforms"?
You don't often get email from hauntsaninja@gmail.commailto:hauntsaninja@gmail.com. Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
+1 to this, I would find frozen_default useful
On Wed, 30 Nov 2022 at 21:19, Eric Traut mailto:eric@traut.com> wrote:
I think this is a reasonable extension. It can be added in a way that's backward compatible with the Python 3.11 typing module and the typing_extensions library because `dataclass_transform` has a `**kwargs` parameter. This would simply require an update to the documentation and an agreement among the type checker maintainers.
I don't think mypy or pytype have implemented support for `dataclass_transform` yet, so it would just be pyre and pyright that would be affected.
I'm willing to add it to pyright if there are no objections and the pyre maintainers are open to making the change.
-Eric
--
Eric Traut
Contributor to Pyright & Pylance
Microsoft