Re: mysqlIndexerTest.test_unicode fails for me
Ralf Schlatterbeck <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.devel |
|---|---|
| Message-ID | <[email protected]> |
On Sun, May 03, 2020 at 09:48:57AM +0200, Ralf Schlatterbeck wrote: > On Fri, May 01, 2020 at 08:50:27PM -0400, John P. Rouillard wrote: > > Also the mysql encoding change is failing in travis: > > > > https://travis-ci.org/github/roundup-tracker/roundup/jobs/681522097#L6967 > > Hmm. This now is a *different* unicode test. > So the test I set out to fix (indexer unicode test) now passes when > passing charset='utf8' to the connect call of mysql. But now another > test breaks with a coding error. Again only for mysql and only with > python2. I haven't looked into it more deeply yet. OK, looks like mysql returns a unicode object if you specify a charset during database connect. I've now changed the String entry in sql_to_hyperdb_value in backends/rdbms_common.py from 'str' to 'us2s'. This converts a unicode value returned from the db to an utf-8 encoded string for py2. I'm in the process of running *all* tests before pushing that fix. Don't hold your breath. Ralf -- Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16 Open Source Consulting www: http://www.runtux.com Reichergasse 131, A-3411 Weidling email: [email protected]