remove notes re: current pymssql DBAPI features

Fixes: #8337
Change-Id: Ib0c107bb386489dcb6d1683f29d0a9574dd96f1e
(cherry picked from commit 319e5a3d8e92ccc97faeeaecd55313131e5a611b)

diff --git a/lib/sqlalchemy/dialects/mssql/pymssql.py b/lib/sqlalchemy/dialects/mssql/pymssql.py
index 84c5fed6f5006fb5f4335130ea695879c7560ba6..c4ec66d117625cf98f8ba484ce720ee5517df7b6 100644 (file)
--- a/lib/sqlalchemy/dialects/mssql/pymssql.py
+++ b/lib/sqlalchemy/dialects/mssql/pymssql.py
@@ -19,24 +19,6 @@ pymssql is a Python module that provides a Python DBAPI interface around
     pymssql is currently not included in SQLAlchemy's continuous integration
     (CI) testing.
 
-Modern versions of this driver worked very well with SQL Server and FreeTDS
-from Linux and were highly recommended. However, pymssql is currently
-unmaintained and has fallen behind the progress of the Microsoft ODBC driver in
-its support for newer features of SQL Server. The latest official release of
-pymssql at the time of this document is version 2.1.4 (August, 2018) and it
-lacks support for:
-
-1. table-valued parameters (TVPs),
-2. ``datetimeoffset`` columns using timezone-aware ``datetime`` objects
-   (values are sent and retrieved as strings), and
-3. encrypted connections (e.g., to Azure SQL), when pymssql is installed from
-   the pre-built wheels. Support for encrypted connections requires building
-   pymssql from source, which can be a nuisance, especially under Windows.
-
-The above features are all supported by mssql+pyodbc when using Microsoft's
-ODBC Driver for SQL Server (msodbcsql), which is now available for Windows,
-(several flavors of) Linux, and macOS.
-
 
 """  # noqa
 import re