How atomic writes using tempfile and os.replace prevent corrupted config files

Writing directly to a file with open(path, 'w') risks corruption if the process is interrupted mid-write, leaving broken or empty content on disk. A safer technique involves writing complete data to a temporary file first, then swapping it in using os.replace(), which operates atomically on both Unix and Windows systems. On POSIX systems, os.replace() maps to the rename(2) kernel call, ensuring the target file is either fully updated or left untouched — never partially written. Python's tempfile.mkstemp() is used to generate a collision-free temp file in the same directory as the target, keeping the swap within a single filesystem. This pattern is especially important in long-running production environments where interruptions such as power outages, forced kills, or antivirus interference are eventually near-certain to occur.