MySQL Connector/Python 1.1.0-alpha has been released
Murthy Narkedimilli <[email protected]>
| Newsgroups | gmane.comp.db.mysql.announce,gmane.comp.db.mysql.general,gmane.comp.db.mysql.packagers |
|---|---|
| Message-ID | <[email protected]> |
Dear MySQL users, MySQL Connector/Python 1.1.0 is the first alpha version of the 1.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 1.1.0-alpha is compatible with MySQL Server versions 5.5 and greater, but should work with earlier versions (greater than 4.1). Python 2.6 and 2.7, as well as Python 3.1 and greater are supported. MySQL Connector/Python 1.1.0-alpha is available for download from http://dev.mysql.com/downloads/connector/python/#downloads The ChangeLog file included in the distribution contains a brief summary of changes in MySQL Connector/Python 1.1.0. For a more complete list of changes, see below or online at: http://dev.mysql.com/doc/relnotes/connector-python/en/ Changes in MySQL Connector/Python 1.1.0 (2013-07-02, Alpha) -------------------------------------------------------------------------------------- Functionality Added or Changed * Incompatible Change: Python v2 code was changed to use new features introduced in Python 2.6 and 2.7. Some examples: + print() is used as a function, not a statement. + Exceptions are handled using the as keyword. + The in keyword is used instead of the has_key() dictionary method. This change means that MySQL Connector/Python 1.1 does not work with version of Python older than 2.6. * Prepared statements now are supported through a new cursor.MySQLCursorPrepared class. * MySQLConnection objects now support a start_transaction() method to begin a transaction. This method accepts arguments indicating whether to use a consistent snapshot and which transaction isolation level to use: cnx.start_transaction(consistent_snapshot=bool, isolation_level=level) The default consistent_snapshot value is False. The default isolation_level value is None, and permitted values are 'READ UNCOMMITTED', 'READ COMMITTED', 'REPEATABLE READ', and 'SERIALIZABLE'. * MySQLConnection objects now support an in_transaction property that returns True or False to indicate whether a transaction is active for the connection. * mysql.connector.__version__ and mysql.connector.__version_info__ now are available to provide MySQL Connector/Python version information in a more standard, Pythonic manner. Bugs Fixed * Relative imports were removed from Python v3 code. PEP-8 indicates that relative imports are discouraged. (Bug #16234372) Documentation -------------------- Online:http://dev.mysql.com/doc/connector-python/en/index.html 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, Murthy -- MySQL Announce Mailing List For list archives: http://lists.mysql.com/announce To unsubscribe: http://lists.mysql.com/announce