Thread: [Conversion Output] KePub Output Plugin
View Single Post
Old 08-02-2021, 09:26 PM   #476
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 Minotaur View Post
Error log attached. This was converting a kepub to a kepub. Quitting Calibre, changing CALIBRE_TEMP_DIR to a dir on my SSD and retrying the same conversion worked perfectly.
The last few lines of the log are:

Code:
  File "concurrent\futures\thread.py", line 57, in run
  File "calibre_plugins.kepubout.container", line 174, in __flush_cache_impl
  File "calibre\ebooks\oeb\polish\container.py", line 1033, in commit_item
OSError: [Errno 22] Invalid argument: 'R:\\TEMP\\calibre_fqq_t_ua\\1o_yka___epub_container\\text\\part0020.html'
At first glance, there doesn't seem to be a problem with that. It looks like a valid path with escaped backslashes. But, Python tends to like forward slashes. It should be the same no matter the location as the same code path is used. I'll have to experiment. How did you created the RAMDrive? It's been years since I have used one.
davidfor is offline   Reply With Quote