Documentation Home
MySQL Connector/Python Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 335.8Kb
PDF (A4) - 337.2Kb

MySQL Connector/Python Release Notes  /  Changes in MySQL Connector/Python 1.0  /  Changes in MySQL Connector/Python 1.0.9 (2013-02-26, General Availability)

Changes in MySQL Connector/Python 1.0.9 (2013-02-26, General Availability)

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 into the build directory, so that the build/lib directory could not be used for development without manually copying (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)