Sunanda Menon MySQL Connector/Python 1.0.9 has been released
Feb 26, 2013; 18:03
Sunanda Menon
MySQL Connector/Python 1.0.9 has been released
Dear MySQL users,
MySQL Connector/Python v1.0.9 is a new version of the 1.0 production release of the pure Python database driver for MySQL.
MySQL Connector/Python version 1.0 is compatible with MySQL Server versions 5.5 and greater, but should work with earlier versions (greater than v4.1). Python v2.6 and greater as well as Python v3.1 and greater are supported. Python v2.4 and v2.5 are known to work, but are not officially supported.
MySQL Connector/Python v1.0.9 is available for download from
A brief summary of changes in MySQL Connector/Python v1.0 is listed below. Please check the ChangeLog file inside the distribution for a more complete list of changes or online at:
Changes in MySQL Connector/Python v1.0.9 ----------------------------------------
Functionality Added or Changed
* Previously, when setting up an SSL connection, the developer had to set the ClientFlag.SSL explicitly in the client_flags argument of the mysql.connector.connect() function call. Now, whenever SSL arguments are specified, the client flag is set automatically. This change makes the SSL behavior of Connector/Python more consistent with other MySQL connectors. (Bug #16217667, Bug #68172)
Bugs Fixed
* The DistUtils command was not copying version.py into the build directory, so that the build/lib directory could not be used for development without manually copying version.py. (Bug #16236136)
* Passing string parameters to a stored procedure resulted in extra quotes being included in the value. This was caused by the conversion from Python to MySQL data types being applied two times. We now only convert once, and pass the values correctly. MySQLCursor.callproc() now also raises a ValueError when the type of an argument is incorrect. (Bug #16217743, Bug #68066)
* Fixed IPv6 for older Microsoft Windows versions. Also improved the associated code for all operating systems: we now use socket.getaddrinfo() instead of inet_pton() to check whether we are connecting using IPv4 or IPv6. A new connection option force_ipv6 has been introduced. When set to True, IPv6 will be used when an address resolves to both IPv4 and IPv6. Otherwise, IPv4 is favored. (Bug #16209119)
The source distribution includes the manual in various formats under the docs/ folder.
Reporting Bugs --------------
We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/
Enjoy!
On Behalf of the MySQL build team at Oracle,
Sunanda Menon
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
Search
Lasso Programming
This site manages and broadcasts several email lists pertaining to Lasso Programming and technologies related and used by Lasso developers. Sign up today!