Context Navigation

Changes between Initial Version and Version 1 of Ticket #20025, comment 2

initial	v1
10	10	http://python.6.n6.nabble.com/MySQL-Django-1-6-Python3-tt5009591.html#a5009904
11	11
12		As of myself, I've done some (very basic) preliminary tests using clelland/MySQL-for-Python-3 alone: Inserting and retrieving data containing non-ASCII characters (é, à, ç, è) appears to work. By examining the output of mysqldump, strings have been correctly encoded at DB level. I performed my tests using both utf8 and latin1 as DB charset. Maybe there is some problems with the integration of both "Django 1.6" and "MySQL for Python 3"?
	12	As of myself, I've done some (very basic) preliminary tests using clelland/MySQL-for-Python-3 alone: Inserting and retrieving data containing non-ASCII characters (é, à, ç, è) appears to work. By examining the output of mysqldump, strings have been correctly encoded at DB level. I performed my tests against MySQL5.1 using both utf8 and latin1 as DB charset. Maybe there is some problems with the integration of both "Django 1.6" and "MySQL for Python 3"?
13	13
14	14	So, if someone could post here some data/link to the possible issues with MySQL-for-Python-3 & Django, that would help things in order ''not'' to drop MySQL support in Python 3 environment.