MySQL Connector/Python 0.1.2 "unicode"
Fixing character set and unicode issues.
Milestone information
- Project:
- MySQL Connector/Python
- Series:
- 0.1
- Version:
- 0.1.2
- Code name:
- unicode
- Released:
- Registrant:
- Geert JM Vanderkelen
- Release registered:
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- No users assigned to blueprints and bugs.
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- No bugs are targeted to this milestone.
Download files for this release
Release notes
o Fixing unicode usage for both Python 2.4+ and 3.1
* Setting 'use_unicode' at connection time is now working.
* conversion.py: removing regular expression for quoting backslashes.
* Adding test case for bug lp:499410
Py3k specific:
* Strings from MySQL are decoded to the given character when use_unicode
is false
* The statement is encoded just before sending it to the MySQL server.
Internally, all is done in unicode.
* In conversion.py: removing _unicode_to_mysql, adding _bytes_to_mysql
* MySQLCursor.
* Removing tests for which the methods were deleted.
o Fix setting character set at connection
* mysql.connector
* Default character set is (still) UTF-8.
* SET NAMES is only used when changing character set after connecting.
Use MySQL.set_
* Test case added for bug report; fixing test case in test_protocol.py
to reflect the new default character set 'utf-8'.
Changelog
This release does not have a changelog.
0 blueprints and 0 bugs targeted
There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.