View Single Post
Old 10-04-2020, 09:41 PM   #521
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by joris0127 View Post
What for some reason seems to work is download and apply metadata for the right book from some other source (i use a plugin for google and amazon) and then click download metadata again to get goodreads information without the idna error. There also seems to be a bigger likelyhood for getting the error when one of the fields contain a , : . or other "weird" tokens.
It works for other metadata sources as the plugin code is different and the web sites are different. But, in this case, I think it is a bug in how Python imports the plugins on Windows. There is calibre beta to fix this issue. This should be released in the next few days, but, you can try the beta now and see if it fixes it for you.
davidfor is offline   Reply With Quote