fix: compatibility with typing_extensions 4.13 and type statement by Daraan · Pull Request #12472 · sqlalchemy/sqlalchemy
marked this pull request as draft
Daraan
marked this pull request as ready for review
sqlalchemy-bot pushed a commit that referenced this pull request
Mar 27, 2025Fixed regression caused by ``typing_extension==4.13.0`` that introduced a different implementation for ``TypeAliasType`` while SQLAlchemy assumed that it would be equivalent to the ``typing`` version. Added test regarding generic TypeAliasType Fixes: #12473 Closes: #12472 Pull-request: #12472 Pull-request-sha: 8861a5a Change-Id: I053019a222546a625ed6d588314ae9f5b34c2f8a (cherry picked from commit 61970f9d2b7809116b5a9d339b45d910e276b428)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters