You seem to be laboring under some kind of misconception. I don't know if I'm interpreting you correctly, but under normal circumstances, a program you write doesn't even have the option of not "doing something": It is a fundamental aspect of a computer that it is constantly executing instructions.
The only way you could truly make a computer "not do anything" would be if you're programming at the hardware level, where you could tell the CPU to halt, but on normal architectures, only the kernel has access to such privileged instructions, and high-level programming languages like Python do not expose them.
What you could do in order to not do anything, at the level of a user program, is to ask the kernel to not schedule your process, such as by executing a call to sleep
, or a blocking I/O call, or the like. Since you're not doing any such thing explicitly, however, there is no alternative for your program other than to execute. Asking to "verify" whether it's doing something is like asking to verify that 1 + 1 = 2
: It's simply true by definition.