[mythtv-users] Important: Changes to Metadata lookup in March 2021

Hika van den Hoven hikavdh at gmail.com
Thu Feb 25 12:37:59 UTC 2021

Hoi Mike,

Thursday, February 25, 2021, 10:40:16 AM, you wrote:

> On 25/02/2021 00:37, Hika van den Hoven wrote:
>> Hoi Peter,
>> Wednesday, February 24, 2021, 7:08:16 PM, you wrote:
>>> Test it by running these
>>> Display help page
>>> /usr/share/mythtv/metadata/Television/tmdb3tv.py -h
>>> Display series data xml
>>> /usr/share/mythtv/metadata/Television/tmdb3tv.py -l en -a US -M Monk
>>> Display episode data xml
>>> /usr/share/mythtv/metadata/Television/tmdb3tv.py -l en -a US -N 1695
>>> "Mr. Monk and the Psychic"
>>> Display episode data xml
>>> /usr/share/mythtv/metadata/Television/tmdb3tv.py -l en -a US -N Monk
>>> "Mr. Monk and the Psychic"
>>> Run the same tests for tvmaze.py
>>> Let me know if this works.
>>> Note: You need to install them on all frontends and backend.
>>> Peter
>> With tmdb3tv I encounter a more complex issue that I as jet do not
>> fully understand. I was missing: https://pypi.org/project/future/0.6.0/
>> that next after installing gave the following error:
>> Traceback (most recent call last):
>>    File "./tmdb3tv.py", line 159, in <module>
>>      sys.exit(main("television",'tmdb3tv.py'))
>>    File "./tmdb3tv.py", line 79, in main
>>      from MythTV.tmdb3.lookup import timeouthandler
>>    File "/usr/lib64/python2.7/site-packages/MythTV/tmdb3/__init__.py", line 5, in <module>
>>      from .tmdb_api import Configuration, searchMovie, searchMovieWithYear, \
>>    File "/usr/lib64/python2.7/site-packages/MythTV/tmdb3/tmdb_api.py", line 69, in <module>
>>      from .request import set_key, Request
>>    File "/usr/lib64/python2.7/site-packages/MythTV/tmdb3/request.py", line 12, in <module>
>>      from .cache import Cache
>>    File "/usr/lib64/python2.7/site-packages/MythTV/tmdb3/cache.py", line 13, in <module>
>>      from .cache_engine import Engines
>>    File "/usr/lib64/python2.7/site-packages/MythTV/tmdb3/cache_engine.py", line 47, in <module>
>>      class CacheEngine(with_metaclass(CacheEngineType, object)):
>>    File "/usr/lib64/python2.7/site-packages/future-0.6.0-py2.7.egg/future/utils/__init__.py", line 125, in with_metaclass
>>      return metaclass('temporary_class', None, {})
>>    File "/usr/lib64/python2.7/site-packages/future-0.6.0-py2.7.egg/future/utils/__init__.py", line 123, in __new__
>>      return type.__new__(cls, name, (), d)
>> TypeError: type() argument 1 must be string, not unicode

> I don't speak python that much, but should the first argument be in single quotes, not double? It is
> a literal, so in theory it shouldn't matter which is used, but I suspect that in this case double
> quotes would be taken as unicode rather than character.

As far as I know single and double quotes are identical in python. You
only can not close the one with the other. I personally always use
single and reserve the double quotes to use inside the text to avoid
having to escape.
That said, it looks sloppy to mix them within one command.

However I tried your suggestion, but to no avail.

Tot mails,
  Hika                            mailto:hikavdh at gmail.com

"Zonder hoop kun je niet leven
Zonder leven is er geen hoop
Het eeuwige dilemma
Zeker als je hoop moet vernietigen om te kunnen overleven!"

De lerende Mens

More information about the mythtv-users mailing list