-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After python3.8 update I receive error #210
Comments
It looks like tvdb_api was importing some internal functions from requests-cache. So not a problem with tvnamer. That appears to have been fixed here, so try updating to the latest version:
|
Many thanks; I'll contact the maintainer from FreeBSD ports, because their latest tvdb_api version was from a year ago. |
Hi, I still could not get it to work. I am at py39 now but I receive this message (FreeBSD 13.1):
Is this a tvnamer error, or a tvdb_api error? Many thanks for your help! Georg |
That might be a problem with requests-cache, or at least an older version of it. Can you tell me what version you have? python -c "import requests_cache; print(requests_cache.__version__)" And are you able to update to a newer version? |
Hi, thanks for your help. I forgot to mention, that meanwhile I have upgraded python to 3.9 and both tvdb_api and tvnamer are py39-. Requests cache is (according to your command): 0.9.2 Thanks again, Georg |
as for the possibility to update to a newer version: the port I have installed is supposedly "required" by tvdb_api to run (see freshports: https://www.freshports.org/www/py-requests-cache93/). I believe the port maintainer specifically forked this version, after I had troubles with requests_cache (see inital post above). However, there seems to be a "newer" port available (version number 0.9.5; https://www.freshports.org/www/py-requests-cache/). As I am a total python noob however, I do not know, whether the "new" 0.9.5 port would change/or fix anything. Since the port maintainer created the 0.9.3 fork specifically for tvdb_api, I do not know, whether installing the 0.9.5 port would change anything (as tvdb_api would possibly continue to use the request_cache 0.9.3). Many thanks for the help, again! G |
Hi, the latest info in the FreeBSD ports community I received is:
Do you think that this is worth a shot? Many thanks! Georg |
tvnamer's classifiers (used for metadata on PyPI) only list python versions up to 3.8, but that doesn't necessarily mean it doesn't work with python 3.9+. Often that just means it hasn't been tested on later versions. I looked into this error a bit more: File "/usr/local/lib/python3.9/site-packages/requests_cache/session.py", line 127, in send
cache_key = self.cache.create_key(request, **kwargs)
TypeError: create_key() got an unexpected keyword argument 'timeout' I had assumed this was a problem with requests-cache's One way or another, a Edit: |
Meanwhile, I can't actually figure out where that |
Many thanks for looking into it. I have the latest versions of both installed, otherwise I would not dare to ask in a forum ;-)
|
Many thanks. I ran tvnamer with the -v option, maybe it is of additional help:
Thank you, I really appreciate the effort (and the tool btw ;-) Georg |
I think we are getting ahead, but not quite there yet. The maintainer of the tvdb_api port included your fix but now I am getting this error:
I am so sorry causing so much trouble, but I just can't give up now that we are about there :-) Georg |
I've created PR dbr/tvdb_api#105 that fixes the issues with new requests-cache. |
Just installed on Debian 12 (bookworm) and applied the above fixes. Works perfectly with python 3.11, THANK YOU!!! |
In Debian 12 i installed the pipx with apt and tvnamer with pipx, according to bellow code sudo apt install pipx
pipx install tvnamer --include-deps
pipx ensurepath Thanks! |
Hi, I recently installed the latest python3.8 update (3.8.13) via pkg (FreeBSD).
Now I receive the following error with tvnamer:
#tvnamer .
Unfortunately I am a Python illiterate. Is this a problem with tvnamer?
Many thanks
Georg
The text was updated successfully, but these errors were encountered: