changes for python 3.14 - pep 649 #12405
Description
Discussed in #12399
Originally posted by hroncok March 5, 2025
Hello, I'm opening this discussion to ask about Python 3.14 support.
In Fedora, we test our packages with pre-releases of Python 3.14. Currently, that is 3.14.0a5.
The tests of sqlalchemy fail on branch main (d9b4d8f), like this:
$ tox --runner virtualenv -e py314 ... sqlalchemy.exc.SAWarning: On class 'Engineer', Column object 'target_id' named directly multiple times, only one will be used: e_target_id, target_id. Consider using orm.synonym instead ... sqlalchemy.exc.IntegrityError: (sqlite3.IntegrityError) NOT NULL constraint failed: person.e_target_id [SQL: INSERT INTO person (e_target_id, target_id) VALUES (?, ?) RETURNING id] [parameters: (None, 1)] (Background on this error at: https://sqlalche.me/e/21/gkpj) ... TypeError: collections.abc.Mapping[str, str] is not a generic class TypeError: collections.abc.MutableMapping[str, str] is not a generic class TypeError: collections.abc.MutableSequence[str] is not a generic class ... sqlalchemy.exc.ArgumentError: Could not locate SQLAlchemy Core type for Python type strtypalias_keyword_nested inside the 'data_one' attribute Mapped annotation ... sqlalchemy.exc.ArgumentError: Could not locate SQLAlchemy Core type for Python type _JsonPep695 inside the 'json1' attribute Mapped annotation ... === 137 failed, 21985 passed, 10854 skipped, 1 warning in 233.53s (0:03:53) === Most of the issues seem related to typing.
Thanks.
(I wanted to report this as an issue, but the text there is quite persistent about opening a discussion first.)