View Single Post
Old 06-28-2016, 09:29 AM   #8
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
Quote:
Originally Posted by DiapDealer View Post
To my knowledge, calibre (and its plugins) ignore any system python environment variables--at least when installed via the recommended calibre installation script. Calibre's python is isolated from any system-installed version of python. So why would setting a system python environment variable affect a calibre plugin? Unless I'm missing something?
It has nothing to do with a "system-installed version of Python". It has to do with Calibre's Python. If you use any of my plug-ins or add-ons that generate calibredb subprocesses (ZMI, CALM, Q&S, and Library Codes), the instructions in their Original Posts must be followed viz a viz generic Python temporary file environment variables, or they will fail for a variety of reasons. In Windows, it would be a security/permissions issue, since the default temporary directory would likely be the directory where calibredb.exe exists.


DaltonST
DaltonST is offline   Reply With Quote