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

MySQL Connector/Python Release Notes  /  Changes in MySQL Connector/Python 8.x  /  Changes in MySQL Connector/Python 8.0.27 (2021-10-19, General Availability)

Changes in MySQL Connector/Python 8.0.27 (2021-10-19, General Availability)

Functionality Added or Changed

  • In Connector/Python 8.0.26, the capability was introduced for applications that use the classic MySQL connections for accounts that use the authentication_kerberos server-side authentication plugin, provided that the correct Kerberos tickets are available or can be obtained from Kerberos. That capability was available on client hosts running Linux only. It is now available on client hosts running Windows.

    For more information about Kerberos authentication, see Kerberos Pluggable Authentication. (WL #14664)

  • Added wheel packages for the commercial edition. (WL #14669)

  • Improved the DMG package as previously it assumed that XCode was installed to provide the Python installation. Additionally, there are now two separate DMG files; one for x86-64 and another for ARM. These installers now provides an option to choose which Python version to use, and defaults to the version provided by XCode. (WL #14688)

  • Added a new converter_str_fallback connection option that allows enabling the conversion to str of value types not supported by the Connector/Python converter class, or by a custom converter class. It defaults to False. (WL #14689)

  • Known limitation: Python 3.10 is not yet supported, and therefore operating systems including Python 3.10 (such as Fedora 35) do not support this or earlier versions of Connector/Python.

    This issue was resolved in 8.0.28.

  • Applications that use legacy MySQL connections can now establish connections without passwords for accounts that use the authentication_oci server-side authentication plugin, provided that the correct configuration entries are available to map to one unique user in a specific Oracle Cloud Infrastructure tenancy.

    To ensure correct account mapping, the client-side Oracle Cloud Infrastructure configuration must contain a fingerprint of the API key to use for authentication (fingerprint entry) and the location of a PEM file with the private part of the API key (key_file entry). Both entries should be specified in the [DEFAULT] profile of the configuration file.

    Unless an alternative path to the configuration file is specified with the new oci_config_file connection option, the following default locations are used:

    • ~/.oci/config on Linux or Posix host types

    • %HOMEDRIVE%%HOMEPATH%/.oci/config on Windows host types

    If the MySQL user name is not provided as a connection option, then the operating system user name is substituted. Specifically, if the private key and correct Oracle Cloud Infrastructure configuration are present on the client side, then a connection can be made without giving any options. (WL #14710)

Bugs Fixed

  • Using the C-extension, attempting to connect with chained SSL certificates using ssl_verify_identity=True did not function. The workaround was to use the pure Python implementation. (Bug #33177337)

  • Printing an mysqlx.result.row object output the generic representation of a class in Python rather than the string value. (Bug #28641350)