MySQL Forums
Forum List  »  Announcements

MySQL Connector/Python 2.1.1 Alpha has been released
Posted by: Karen Langford
Date: February 23, 2015 12:47PM

Dear MySQL users,

MySQL Connector/Python 2.1.1-alpha is the first alpha version of
2.1 release series of the pure Python database driver for MySQL.
It is intended to introduce users to the new features.

This release is not feature complete but it should be stable
enough for users to understand the new features and how we
expect them to work.

As is the case with all non-GA releases, it should not be used
in any production environment.

MySQL Connector/Python version 2.1.1-alpha is compatible with MySQL
Server versions 5.5 and greater. Python 2.6 and greater as well as
Python 3.3 and greater are supported. Python 2.4, 2.5 and 3.1, 3.2
are not supported.

MySQL Connector/Python 2.1.1-alpha is available for download from:

The ChangeLog file included in the distribution contains a brief summary
of changes in MySQL Connector/Python 2.1.1. For a more complete list of
changes, see below or online at:


Changes in MySQL Connector/Python 2.1.1 (2015-02-23)

   C Extension Notes

     * MySQL Connector/Python distributions now are available
       that include a C Extension that interfaces with the MySQL
       C client library. For queries that return large result
       sets, using the C Extension can improve performance
       compared to a "pure Python" implementation of the MySQL
       client/server protocol.
       For binary Connector/Python distributions, some packaging
       types have a single distribution file that includes the
       pure-Python Connector/Python code together with the C
       Extension. (Windows MSI and OS X Disk Image packages fall
       into this category.) Other packaging types have two
       related distribution files: One that includes the
       pure-Python Connector/Python code, and one that includes
       only the C Extension. For packaging types that have
       separate distribution files, install both distributions
       if you want to use the C Extension. The two files have
       related names, the difference being that the one that
       contains the C Extension has "cext" in the distribution
       file name.
       Source distributions include both the pure-Python code
       and the C Extension, and distribution names do not
       contain "cext". Instead, availability of the C Extension
       is determined by whether you compile the distribution
       with the --with-mysql-capi option.
       Packages for Connector/Python with the C Extension are
       available at the Connector/Python download site
       ( For
       installation instructions, see Connector/Python
       For information about using the
       C Extension, see The Connector/Python C Extension
       For Connector/Python installations that support the C
       Extension, the use_pure connection argument to connect()
       controls whether to use the extension. If use_pure is
       True (the default), the connection uses pure Python. If
       use_pure is False, the connection uses the C Extension.
       It is also possible to use the C Extension directly, by
       importing the _mysql_connector module rather than the
       mysql.connector module. See The _mysql_connector C
       Extension Module

   Bugs Fixed

     * With mysql.connector.django as the engine, the python inspectdb command failed with an "Unread result
       found" error. (Bug #20022533)

     * If the pool_size and pool_name connection arguments were
       specified using the option file (as opposed to being
       passed explicitly to the connect call), the pooled
       connection was successfully created, but an exception was
       raised when closing it. (Bug #19549363)

     * The Django backend raised an exception when converting
       "0000-00-00 00:00:00" to None. (Bug #73940, Bug

     * The type_code in cursor.description did not compare equal
       to any of the type objects defined in
       mysql.connector.dbapi. (Bug #73798, Bug #19584051)

     * Data corruption occurred when inserting sufficiently
       large data in a table with a TEXT type column using
       prepared statements, due to incorrect encoding of the
       data length while sending the prepared statement packet.
       (Bug #73690, Bug #19522948)

     * When the character set was binary, character set
       conversion could occur. Conversion is no longer done and
       binary data is returned as is. (Bug #71909, Bug

The source distribution includes the manual in various formats under
the docs/ folder.

Reporting Bugs
We welcome and appreciate your feedback and bug reports:

Enjoy !

On Behalf of the MySQL RE team at Oracle

Options: ReplyQuote

Written By
MySQL Connector/Python 2.1.1 Alpha has been released
February 23, 2015 12:47PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.