MSK Institute • Shikohabad
Loading Page Content...
Preparing courses, live labs, and learning resources.सामग्री लोड हो रही है, कृपया प्रतीक्षा करें...
Connecting serverPlease wait...
💻 Practical Labs🚀 Free Demo📜 Verified Certificates
Preparing courses, live labs, and learning resources.सामग्री लोड हो रही है, कृपया प्रतीक्षा करें...
In Python's threading module, threads are categorized into two fundamental operational modes: Non-Daemon (Foreground) threads and Daemon (Background) threads. The distinction directly governs how the CPython interpreter behaves during application shutdown and whether running threads prevent the process from terminating.
When a Python script begins execution, the initial main thread is created as a non-daemon thread. The CPython runtime enforces a strict shutdown rule:
A thread's daemon status is determined by its daemon property or parameter:
daemon = True before calling thread.start(). Modifying daemon on an already active thread raises a runtime error:
RuntimeError: cannot set daemon status of active thread.Because the operating system terminates daemon threads abruptly when all non-daemon threads exit, cleanup code inside finally blocks or context managers is not guaranteed to execute:
| Characteristic | Non-Daemon (Default) | Daemon (daemon=True) |
|---|---|---|
| Prevents Exit? | Yes: Process waits for completion | No: Abruptly terminated on process exit |
| Cleanup Guarantee | finally blocks always execute | finally blocks may be skipped entirely |
| Configuration | Default behavior (daemon=False) | Explicitly set via daemon=True |
| Modification Window | Before or after (default) | Must be set before start() |
| Primary Domain | Critical data processing, file writes | Ephemeral background monitors, telemetry |
Daemon threads terminate abruptly when all non-daemon threads finish. Any open files, active database transactions, or network connections held by daemon threads may be left in a corrupted state.
thread.join()Calling thread.join() without a timeout parameter can hang the main program indefinitely if a worker thread deadlocks or crashes silently.
Create a daemon thread that prints a heartbeat ping every 100ms. Demonstrate that the daemon terminates automatically when the main non-daemon thread finishes.
What happens to active daemon threads when the main thread and all other non-daemon threads finish execution? A. The Python process freezes until the daemon threads complete. B. Daemon threads are abruptly terminated immediately by the operating system, and the process exits. C. Daemon threads are converted into operating system system services. D. A RuntimeError is raised.
At what point must the daemon status of a thread be configured? A. At any time, even while the thread is running. B. Exclusively before calling thread.start(). C. Only after calling thread.join(). D. Inside the thread's run() method.
daemon attribute on an active thread raises RuntimeError: cannot set daemon status of active thread. It must be configured prior to .start().Why is it dangerous to perform transactional file writes or database commits inside a daemon thread? A. Daemon threads do not have write access to the filesystem. B. When the main program terminates, daemon threads are terminated abruptly, bypassing finally blocks and potentially corrupting data. C. Daemon threads run at half CPU clock frequency. D. Database drivers do not support daemon threads.
finally or __exit__ blocks does not execute, leading to corrupted or incomplete files.What is the default daemon status of a new thread created via threading.Thread(target=my_func) by the main thread? A. True B. False (Non-daemon) C. None D. Inherits from the operating system kernel setting
daemon flag from the thread that created it. Because the main thread is non-daemon (daemon=False), newly spawned threads are non-daemon by default unless explicitly marked otherwise.Which of the following tasks is the most appropriate use case for a daemon thread? A. Processing credit card transactions and updating ledger files. B. A periodic background telemetry agent that samples CPU load every 5 seconds. C. A database migration runner. D. Compressing a multi-gigabyte video file to disk.
In the next lesson, we will continue your advanced Python journey with Project: Multithreaded Downloader (6: Multithreading in Python).
👉 Continue to Next Lesson: Project: Multithreaded Downloader →
Continue learning with hands-on practice, examples, and exercises in the upcoming topic.
| Previous Lesson | Next Lesson |
|---|---|
| Thread Synchronization | Python 3.13+ Free-Threaded Execution (No-GIL PEP 703) and JIT Compiler |
Test your understanding of this lesson with 5 questions. Each question has one correct answer.