Python’s print() function defaults to writing to the console, but it also accepts a file keyword argument that redirects output to any writable file object. This works with any object that has a .write() method — files, io.StringIO, and similar streams. The idiomatic approach pairs print() with a context-managed file handle using with open(\u2026) as f:, which handles closing automatically.<\/p>\n\n\n\n
Redirecting print() to a file is useful for logging during development, saving script output to disk without modifying program logic, and writing data export pipelines where you want human-readable output. Four common approaches exist, ranging from the recommended print(file=f) pattern to sys.stdout redirection and the logging module.<\/p>\n\n\n\n
print('text', file=f)<\/code> with with open(path, 'w') as f:<\/code> — the standard approach<\/li>\n\n\n\n- Pass
file=f<\/code> explicitly — avoid sys.stdout<\/code> redirection for normal file output<\/li>\n\n\n\n- Use mode
'w'<\/code> to overwrite or 'a'<\/code> to append. print()<\/code> adds newlines automatically, unlike f.write()<\/code><\/li>\n\n\n\n- For production logging, use the
logging<\/code> module with FileHandler<\/code> instead of print()<\/code><\/li>\n<\/ul>\n\n\n\nThe print(file=f) Approach<\/h2>\n\n\n\n
The print()<\/code> function accepts a file<\/code> keyword argument that accepts any file-like object. The recommended pattern uses a context manager:<\/p>\n\n\n\nwith open("output.txt", "w") as f:\n print("First line", file=f)\n print("Second line", file=f)\n print("Third line", file=f)\n\n<\/pre><\/div>\n\n\nAfter running this, output.txt<\/code> contains three lines. The context manager closes the file automatically when the with<\/code> block exits, even if an exception occurs.<\/p>\n\n\n\nTo append instead of overwriting, change the mode to 'a'<\/code>:<\/p>\n\n\n\nwith open("output.txt", "a") as f:\n print("Appended line", file=f)\n\n<\/pre><\/div>\n\n\nf.write() vs print(file=f)<\/h2>\n\n\n\n
The f.write()<\/code> method and print(file=f)<\/code> behave differently:<\/p>\n\n\n\n# write() does NOT add a newline by default\nwith open("output.txt", "w") as f:\n f.write("Line 1")\n f.write("Line 2") # Appears right after Line 1 on the same line\n\n# print() automatically adds a newline (unless end="")\nwith open("output.txt", "w") as f:\n print("Line 1", file=f)\n print("Line 2", file=f) # Each on its own line\n\n<\/pre><\/div>\n\n\nUse f.write()<\/code> when you need precise control over what gets written — no automatic newlines, no spaces. Use print(file=f)<\/code> for convenient line-by-line output where the newline should be added automatically.<\/p>\n\n\n\nOne common mistake is opening the file without a context manager:<\/p>\n\n\n
\n# WRONG - file is never explicitly closed\nprint("Data", file=open("output.txt", "w"))\n\n# RIGHT - context manager ensures close\nwith open("output.txt", "w") as f:\n print("Data", file=f)\n\n<\/pre><\/div>\n\n\nRedirecting sys.stdout<\/h2>\n\n\n\n
Python’s sys.stdout<\/code> is a file-like object that print()<\/code> writes to by default. You can replace it with a custom file object to capture all print()<\/code> calls:<\/p>\n\n\n\nimport sys\n\n# Save original stdout\noriginal_stdout = sys.stdout\n\n# Redirect all print() calls to a file\nwith open("output.txt", "w") as f:\n sys.stdout = f\n print("This goes to the file")\n print("So does this")\n\n# Restore stdout\nsys.stdout = original_stdout\n\nprint("This prints to the console")\n\n<\/pre><\/div>\n\n\nThis approach works but has significant drawbacks: it affects the entire process, makes debugging harder because console output disappears, and must be carefully restored or the program crashes. Reserve sys.stdout<\/code> redirection for situations where you genuinely need to intercept all output — not for normal file writing.<\/p>\n\n\n\nUsing the logging Module<\/h2>\n\n\n\n
The logging<\/code> module is the right choice for production-grade file output. It supports multiple severity levels, log rotation, and structured output. The simplest file configuration uses basicConfig<\/code>:<\/p>\n\n\n\nimport logging\n\nlogging.basicConfig(\n filename="app.log",\n level=logging.DEBUG,\n format="%(levelname)s: %(message)s"\n)\n\nlogging.debug("Debug info")\nlogging.info("Process started")\nlogging.warning("Low memory")\n\n<\/pre><\/div>\n\n\nFor more control, use FileHandler<\/code> directly:<\/p>\n\n\n\nimport logging\n\nlogger = logging.getLogger(__name__)\nlogger.setLevel(logging.DEBUG)\n\nfile_handler = logging.FileHandler("app.log")\nfile_handler.setLevel(logging.DEBUG)\n\nformatter = logging.Formatter("%(asctime)s - %(levelname)s - %(message)s")\nfile_handler.setFormatter(formatter)\n\nlogger.addHandler(file_handler)\nlogger.info("Application running")\n\n<\/pre><\/div>\n\n\nThe logging<\/code> module is superior to print()<\/code> for any output that survives beyond development — it supports rotation, multiple handlers, and configurable severity thresholds.<\/p>\n\n\n\nCommon Pitfalls<\/h2>\n\n\n\n\n- Forgetting to close the file.<\/strong> Opening a file without a context manager or explicit
.close()<\/code> can leave data unflushed. Always use with open(...) as f:<\/code>.<\/li>\n\n\n\n- Using
'w'<\/code> instead of 'a'<\/code>.<\/strong> Write mode ('w'<\/code>) truncates the file before writing. Append mode ('a'<\/code>) preserves existing content and adds to the end.<\/li>\n\n\n\n- Mixing
write()<\/code> and print(file=f)<\/code> on the same handle.<\/strong> Both work, but they have different buffering behavior. Pick one approach per file and stick with it.<\/li>\n\n\n\n- Printing to a closed file.<\/strong> If the context manager block exits before all prints complete, the file closes and subsequent writes raise
ValueError: I\/O operation on closed file<\/code>.<\/li>\n<\/ul>\n\n\n\nFAQ<\/h2>\n\n\n\n
Q: Does print(file=f) automatically flush the data?<\/strong><\/p>\n\n\n\nBy default, print()<\/code> flushes its output when a newline is written (the end=\"\\n\"<\/code> default). To flush immediately without a newline, use print(value, file=f, flush=True)<\/code>.<\/p>\n\n\n\nQ: Can print() write to a file opened in binary mode?<\/strong><\/p>\n\n\n\nprint()<\/code> writes text to files opened in text mode (the default). For binary output, use f.write()<\/code> on a file opened with \"wb\"<\/code> — print()<\/code> raises a TypeError<\/code> on binary file handles.<\/p>\n\n\n\nQ: How is print(file=f) different from sys.stdout redirection?<\/strong><\/p>\n\n\n\nprint(file=f)<\/code> explicitly targets a single file object and leaves sys.stdout<\/code> unchanged. sys.stdout<\/code> redirection affects every print()<\/code> call in the entire process and requires manual restoration.<\/p>\n\n\n\nQ: Can I print to stdout and a file at the same time?<\/strong><\/p>\n\n\n\nYes — write to stdout explicitly while also writing to the file, or use tee<\/code>-style logic where each print goes to both destinations. The logging<\/code> module handles this with multiple handlers.<\/p>\n\n\n\nQ: Does the logging module overwrite or append to the log file?<\/strong><\/p>\n\n\n\nBy default, FileHandler<\/code> opens the file in append mode. Pass mode='w'<\/code> when creating the handler to overwrite instead: FileHandler(\"app.log\", mode='w')<\/code>.<\/p>\n","protected":false},"excerpt":{"rendered":"Python’s print() function defaults to writing to the console, but it also accepts a file keyword argument that redirects output to any writable file object. This works with any object that has a .write() method — files, io.StringIO, and similar streams. The idiomatic approach pairs print() with a context-managed file handle using with open(\u2026) as […]<\/p>\n","protected":false},"author":7,"featured_media":67613,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-2836","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-built-in-methods"],"_links":{"self":[{"href":"https:\/\/www.askpython.com\/wp-json\/wp\/v2\/posts\/2836","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.askpython.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.askpython.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.askpython.com\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.askpython.com\/wp-json\/wp\/v2\/comments?post=2836"}],"version-history":[{"count":0,"href":"https:\/\/www.askpython.com\/wp-json\/wp\/v2\/posts\/2836\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.askpython.com\/wp-json\/wp\/v2\/media\/67613"}],"wp:attachment":[{"href":"https:\/\/www.askpython.com\/wp-json\/wp\/v2\/media?parent=2836"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.askpython.com\/wp-json\/wp\/v2\/categories?post=2836"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.askpython.com\/wp-json\/wp\/v2\/tags?post=2836"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}