id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc,mlocked 13123,Exception using python bindings,tom@…,Roger Siddons,"With recent versions of the python MySQLdb library you can get an exception when the MythTV python bindings do executemany: {{{ Traceback (most recent call last): File ""./mythcommflag-silence"", line 250, in main() File ""./mythcommflag-silence"", line 217, in main rec.update() File ""/usr/lib/python2.7/site-packages/MythTV/database.py"", line 429, in update self._push() File ""/usr/lib/python2.7/site-packages/MythTV/dataheap.py"", line 354, in _push self.markup.commit() File ""/usr/lib/python2.7/site-packages/MythTV/database.py"", line 624, in commit ','.join(['?' for a in fields])), data) File ""/usr/lib/python2.7/site-packages/MythTV/_conn_mysqldb.py"", line 96, in executemany raise MythDBError(MythDBError.DB_RAW, e.args) MythTV.exceptions.MythDBError: MySQL error: sequence item 0: expected string, bytearray found }}} The problem is that executemany calls back to the logged cursor with the query expressed as a bytearray that has been encoded using the database encoding. That then throws an exception because you can't use join on a bytearray. I have opened https://github.com/MythTV/mythtv/pull/153 with a patch to decode back to a string in this case.",Patch - Bug Fix,closed,minor,29.1,Bindings - Python,0.28.1,medium,fixed,,,0