Kevin M

@simonmcnair this might be related to the hang which is a CPython bug I reported years ago https://github.com/python/cpython/issues/87950 ... and you mentioned you're using it in Linux, but the output...

The CPython bug manifests itself when you initialize the `ExifToolHelper` and depend on the destructor to stop the process. The way to work around the bug is to destruct the...

CPython 3.12 seems to fix this entire issue btw

Ok. I also have an issue with running in pytest on actual Windows. I think this might be related to the bug I reported to CPython more than a year...

Hmm, that's odd that the singleton is terminating the `exiftool` process after each execute... anyways, Mac and Windows works slightly differently in terms of the "thread spawning at python interpreter...

I'll try this next week. But from what I remember, there bug manifests itself during __del__ or something. I had some tests cases that caused PyExifTool to hang. I think...

So, currently PyExifTool doesn't support any type of progress. I could envision doing something like a callback to dump out the os.read() somewhere... but I'm not necessarily sure this would...

@Yang-z you can set that encoding to your option by setting the `ExifTool.encoding` property to 'utf-8' The code was changed because not all locales use UTF-8 by default, and it...

@Yang-z this is some good information. I've read through the comments once already but I'm going to try again to understand and see if some improvements can be made to...

It would be good programming if you added `print(params)` to see if what params are actually passed I'm unable to replicate this issue on Windows, and I'm not even sure...