My guess is that the environment (eg, PATH, PYTHONPATH etc) for the new
explorer instance isn't setup correctly - how is the explorer.exe
process started when it *does* work? It's hard to answer without more
info, but Python ends up inside explorer.exe, so the environment that
explorer.exe star
On 7/01/2016 6:21 AM, Alexander Jewell wrote:
Unfortunately my end goal was to bundle the entire application as an exe
with PyInstaller so that the end user does not actually have Python
installed.
Do you think it would be possible to package the overlay handler in such
a way that explorer would
Thanks for the reply Mark.
That makes sense, I hadn't thought about the environment.
During development I'm testing in a virtual environment which contains
Python 3.4 and all the required libraries. The explorer.exe process is
killed and started by the same process (within the same script) that
re
