From 78833af4e650d37e6257cfbb541e4db56e2a285f Mon Sep 17 00:00:00 2001 From: Federico Caselli Date: Sun, 27 Nov 2022 18:11:34 +0100 Subject: update for mypy 1.0 dev As I need dmypy to work without facing [1], I am running the latest build of mypy which seems so far to finally not have that issue. update constructs that latest mypy is being more picky about, including better typing for the _NONE_NAME symbol used in constraints (porting those elements from the Enum patch at I15ac3daee770408b5795746f47c1bbd931b7d26d) [1] https://github.com/python/mypy/issues/12744 Change-Id: Ib3f56787fa65ea9bb2e6a0bccc4d99f54c516dad --- lib/sqlalchemy/sql/elements.py | 3 --- 1 file changed, 3 deletions(-) (limited to 'lib/sqlalchemy/sql/elements.py') diff --git a/lib/sqlalchemy/sql/elements.py b/lib/sqlalchemy/sql/elements.py index 6a9bd74ca..eff8c9bc1 100644 --- a/lib/sqlalchemy/sql/elements.py +++ b/lib/sqlalchemy/sql/elements.py @@ -5112,9 +5112,6 @@ class conv(_truncated_label): __slots__ = () -_NONE_NAME = util.symbol("NONE_NAME") -"""indicate a 'deferred' name that was ultimately the value None.""" - # for backwards compatibility in case # someone is re-implementing the # _truncated_identifier() sequence in a custom -- cgit v1.2.1