[mythtv-users] mythcal error with 0.22-fixes

Michael T. Dean mtdean at thirdcontact.com
Mon Nov 23 00:15:53 UTC 2009

On 11/22/2009 02:05 PM, John Finlay wrote:
> Michael T. Dean wrote:
>> On 11/21/2009 02:26 PM, John Finlay wrote:
>>> David Knight wrote:
>>>> I've pulled down the latest version of mythcal from google code
>>>> (http://code.google.com/p/mythcal/), installed the pytz and
>>>> python-gdata
>>>> prerequisites but get the following error when running mythcal
>>>> --dry-run:
>>>> Traceback (most recent call last):
>>>>   File "./mythcal", line 106, in <module>
>>>>     recordings = get_recordings_from_backend()
>>>>   File "./mythcal", line 98, in get_recordings_from_backend
>>>>     if mythtv.isRecording(recorder):
>>>>   File "usr/lib/python2.5/site-packages/MythTV/MythTV.py", line
>>>> 295, in
>>>> isRecording
>>>> TypeError: sequence item 0: expected string, int found   
>>> Looks like the MythTV API was changed when the bindings were
>>> updated. isRecording will not accept an int anymore so mythcal will
>>> have to pass a string or MythTV would  have to be changed to support
>>> the previous API. Looks like the getCurrentRecording binding has
>>> been changed in this fashion as well.
>> Ah, though now I see you're pointing out that it does use the MythTV
>> Python bindings.  That means it just needs updated for the new API
>> version--which should be much easier than updating for a new protocol
>> version.
> I would also file a bug report against MythTV.py for the change in API
> since it's possible the API change was unintentional. This change is
> likely to cause breakage in other apps. 

There were many intentional API changes in the MythTV Python bindings
with the 0.22 release of the MythTV Python bindings.  They went from
mostly useless to better than the Perl bindings because of such API changes.


More information about the mythtv-users mailing list