From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Thu, 30 Mar 2023 14:14:23 +0000 (-0400)
Subject: add mypy issue 13856 to bug reporting template
X-Git-Tag: rel_2_0_8~11
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=254d621c33dd18fe5f3b8564e9b017a37ac8e029;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

add mypy issue 13856 to bug reporting template

Change-Id: Ie25810bfb188794858ba39e246a72b06c484e474
References: #9567
---

diff --git a/.github/ISSUE_TEMPLATE/typing.yaml b/.github/ISSUE_TEMPLATE/typing.yaml
index bf21a5f074..28149f651d 100644
--- a/.github/ISSUE_TEMPLATE/typing.yaml
+++ b/.github/ISSUE_TEMPLATE/typing.yaml
@@ -35,6 +35,21 @@ Currently the SQLAlchemy team is targeting mypy support, with best effort suppor
         - label: The api is not in a module listed in [#6810](https://github.com/sqlalchemy/sqlalchemy/issues/6810) so it should pass type checking
           required: true
 
+  - type: checkboxes
+    id: mypy13856
+    attributes:
+      label: Confirm this is not Mypy dataclasses issue 13856
+      description: "Mypy 1.1.1 has a bug in its pep-681 implementation that affects SQLAlchemy
+      ``MappedAsDataclass``.  If the issue is using Mypy 1.1.1 and involves attribute types
+      for a ``MappedAsDataclass`` class, please consult the workarounds at
+      https://docs.sqlalchemy.org/en/20/orm/dataclasses.html#declarative-dataclass-mapping to
+      disable pep-681 for Mypy.
+
+      "
+      options:
+        - label: This is not related to Mypy issue 13856
+          required: true
+
   - type: textarea
     attributes:
       label: Describe the typing issue