Problems killing a tkinter app when a time expiry is detected.

[ttodd54-beep]

I have a python 3.7 tkinter app that I'm packing into a single exe using pyarmor. I'm setting an expiry date using -e and setting a --period to check on the expiry. When an expiry occurs, I would like the app to die completely, but instead, it ends up in a state where some of the functionality is disabled, and others still work.

My understanding of this has to do with tkinter capturing exceptions and continuing on. Is there is a simple way to fix this? I'm ok without doing a graceful shutdown. I've tried several suggestions from Gemini that didn't work.

Thanks!
Terry

[jondy]

Refer to this section
https://pyarmor.readthedocs.io/en/latest/tutorial/advanced.html#customization-error-handler

[ttodd54-beep]

Thanks so much for your reply.

I did some testing using on_error=2 and it was more aggressive in terminating the app. But the same sort of behavior occurs, in that some parts of the app may function, but other parts may lead to an immediate killing of the app.

Is there any way I can intercept the exception that is created when the expiry date is violated, so that I could kill the app completely at that point?

[jondy]

Also check this note about --period
https://pyarmor.readthedocs.io/en/latest/reference/man.html#cmdoption-pyarmor-gen-period

And please check the online doc section inside into pack to make sure all the scripts in this app are obfuscated.
https://pyarmor.readthedocs.io/en/latest/topic/repack.html

Besides, please check this guide to read the doc
https://pyarmor.readthedocs.io/en/latest/questions.html#asking-questions-in-github