diff options
author | Federico Caselli <CaselIT@users.noreply.github.com> | 2023-04-14 19:34:21 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-04-14 19:34:21 +0200 |
commit | 6f3c741e41e13624d63f4faa4bdcec8466bda7f4 (patch) | |
tree | 23aca71da7a32066797ced7de096dc4f879ba8dd | |
parent | d1b1ca04323ba3f294c910b8d94153f307370651 (diff) | |
download | sqlalchemy-6f3c741e41e13624d63f4faa4bdcec8466bda7f4.tar.gz |
Remove mypy dataclass reference (#9651)
-rw-r--r-- | .github/ISSUE_TEMPLATE/typing.yaml | 15 |
1 files changed, 0 insertions, 15 deletions
diff --git a/.github/ISSUE_TEMPLATE/typing.yaml b/.github/ISSUE_TEMPLATE/typing.yaml index 28149f651..bf21a5f07 100644 --- a/.github/ISSUE_TEMPLATE/typing.yaml +++ b/.github/ISSUE_TEMPLATE/typing.yaml @@ -35,21 +35,6 @@ 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 |