Opened 8 years ago

Closed 8 years ago

#9279 closed Bug Report (Fixed)

Mirobridge failure with Python 2.7 and oursql

Reported by: anonymous Owned by: Raymond Wagner
Priority: minor Milestone: 0.25
Component: Contributed Scripts & Apps Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

I'm testing Fedora 14 with trunk revision 27314. Per commit 27184 regarding Python 2.7 I have installed ousql (with the patch at https://bugs.launchpad.net/oursql/+bug/672059) and set the ENABLE_OURSQL environment variable. It appears that oursql is found and utilized, however, mirobridge errors running at configuration test with:

$ python /usr/share/doc/mythtv-docs-0.24/contrib/imports/mirobridge/mirobridge.py -t 2010-11-23 15:52:49,044 - mirobridge - INFO - Using python library 'pyparsing' version 1.5.5 2010-11-23 15:52:49,777 - mirobridge - INFO - Miro Bridge version v0.6.6 with Miro version 3.5 2010-11-23 15:52:49,779 - mirobridge - INFO - Using mirobridge_interpreter_3_5_0 2010-11-23 15:52:49,870 - mirobridge - INFO - Traceback (most recent call last):

File "/usr/share/doc/mythtv-docs-0.24/contrib/imports/mirobridge/mirobridge.py", line 2649, in <module>

main()

File "/usr/share/doc/mythtv-docs-0.24/contrib/imports/mirobridge/mirobridge.py", line 2137, in main

if getStorageGroups() == False:

File "/usr/share/doc/mythtv-docs-0.24/contrib/imports/mirobridge/mirobridge.py", line 659, in getStorageGroups

if dirname[-1:] == u'/':

UnboundLocalError?: local variable 'dirname' referenced before assignment

Change History (2)

comment:1 Changed 8 years ago by Raymond Wagner

Component: MythTV - GeneralContributed Scripts & Apps
Milestone: unknown0.25
Owner: set to Raymond Wagner
Status: newaccepted
Version: UnspecifiedTrunk Head

comment:2 Changed 8 years ago by Raymond Wagner

Resolution: Fixed
Status: acceptedclosed

(In [27327]) Fix mirobridge to pass storagegroup directory name through unchanged if it is already unicode. Closes #9279 for now. Refs #8768. If this is going to be a recurring issue, it may be better to for all strings outputted by the MySQLdb module to unicode as well for consistency, and deal with whatever code needs to be fixed as a result.

Note: See TracTickets for help on using tickets.