Is your feature request related to a problem? Please describe.
The mssql-python package currently appears to provide wheels for CPython up to Python 3.14 (cp314), with no compatible wheels available for Python 3.15.
This prevents projects upgrading to Python 3.15 from reliably installing the driver. For example, our Cortex application uses mssql-python to connect to Azure SQL, including through SQLAlchemy's mssql+mssqlpython dialect. Dependency resolution and installation with uv lock and uv sync fail when targeting Python 3.15.
Describe the solution you'd like
Add Python 3.15 support and publish compatible CPython 3.15 (cp315) wheels on PyPI.
The published wheels should support installing and using the driver on Python 3.15, including Azure SQL connectivity and SQLAlchemy integration.
Describe alternatives you've considered
- Staying on Python 3.14 until compatible wheels are available.
- Replacing
mssql-python with an alternative driver, such as pyodbc, which would require additional changes to our database connectivity and SQLAlchemy integration.
Publishing Python 3.15-compatible wheels would be the simplest solution for downstream projects.
Additional context
Is Python 3.15 support already planned? If so, is there an estimated timeline for publishing compatible wheels?
Is your feature request related to a problem? Please describe.
The
mssql-pythonpackage currently appears to provide wheels for CPython up to Python 3.14 (cp314), with no compatible wheels available for Python 3.15.This prevents projects upgrading to Python 3.15 from reliably installing the driver. For example, our Cortex application uses
mssql-pythonto connect to Azure SQL, including through SQLAlchemy'smssql+mssqlpythondialect. Dependency resolution and installation withuv lockanduv syncfail when targeting Python 3.15.Describe the solution you'd like
Add Python 3.15 support and publish compatible CPython 3.15 (
cp315) wheels on PyPI.The published wheels should support installing and using the driver on Python 3.15, including Azure SQL connectivity and SQLAlchemy integration.
Describe alternatives you've considered
mssql-pythonwith an alternative driver, such aspyodbc, which would require additional changes to our database connectivity and SQLAlchemy integration.Publishing Python 3.15-compatible wheels would be the simplest solution for downstream projects.
Additional context
uvmssql+mssqlpythonIs Python 3.15 support already planned? If so, is there an estimated timeline for publishing compatible wheels?