Closed greateggsgreg closed 6 months ago
Can you elaborate why do you want to do this? this leads to non-deterministic behavior also see https://github.com/py4n6/pytsk/issues/75
Creating a work-around for a work-around is not a good idea, closing in favor of patching the sleuthkit source https://github.com/py4n6/pytsk/pull/102
Ah thank you that'll work as well @joachimmetz
Programs may rely on a consistent, non-UTC timezone, for logging / other behaviors. When pytsk3 is imported, this code will may change the timezone in the middle of a program run which has adverse effects. I do understand this is to correct libtsk behavior, however, this is a way to opt-out of the forced tzset and handle libtsk's timestamp behavior separately.