Cross-Platform File Handling in Python

Why Runtime Context Matters

Reading the Python Runtime

import sys

version = sys.version_info
print(version.major)
print(version.minor)
print(version.micro)
print(version.releaselevel)

Branching by Operating System

1. 1
   Evaluate platform.platform().startswith('Windows').
2. 2
   If the result is True, retrieve HOMEDRIVE and HOMEPATH.
3. 3
   If the result is False, retrieve HOME.
4. 4
   Pass the selected directory and test.log to os.path.join().
5. 5
   Use the resulting logging_file value after the branch completes.

Joining Directory Components

import os
import platform
import logging

if platform.platform().startswith('Windows'):
    logging_file = os.path.join(
        os.environ['HOMEDRIVE'] + os.environ['HOMEPATH'],
        'test.log'
    )
else:
    logging_file = os.path.join(
        os.environ['HOME'],
        'test.log'
    )

logging.basicConfig(
    filename=logging_file,
    level=logging.DEBUG
)

Filtering and Routing Log Messages

Tracing the Divergence Point

Mistakes Beginners Make

• ✕Common mistake

  Manually writing one separator style into a cross-platform path.

  What it looks like

  Combining a directory and test.log with a separator chosen for only one operating system.

  Why it fails

  The source pattern uses os.path.join() because it handles the platform-specific separator.

  Do this instead

  Pass the directory and file name to os.path.join().

• ✕Common mistake

  Assuming both platform branches execute.

  What it looks like

  Tracing the HOMEDRIVE and HOMEPATH branch and the HOME branch as though both assign logging_file.

  Why it fails

  The if/else decision selects one branch based on platform.platform().startswith('Windows').

  Do this instead

  Record whether the platform test is True or False, then trace only the selected branch.

• ✕Common mistake

  Treating a version as an unstructured string when structured fields are available.

  What it looks like

  Parsing a version string instead of inspecting sys.version_info.

  Why it fails

  sys.version_info already provides major, minor, micro, and releaselevel components.

  Do this instead

  Inspect the named components of sys.version_info for version-specific logic.

• ✕Common mistake

  Expecting lower-severity messages when the logging threshold is WARNING.

  What it looks like

  Looking for DEBUG messages while logging is configured at WARNING.

  Why it fails

  Logging levels act as filters, and WARNING discards lower-severity messages.

  Do this instead

  Use DEBUG when broad debugging output is needed, or choose a higher threshold deliberately.

Trace It Yourself

1. 1
   Inspect the major, minor, micro, and releaselevel fields in sys.version_info.
2. 2
   Evaluate platform.platform().startswith('Windows').
3. 3
   Identify the environment variables used by the selected branch.
4. 4
   Trace the directory and test.log into os.path.join().
5. 5
   Follow logging_file into logging.basicConfig() and check the configured level.

Key Takeaways

1. 1
   sys.version_info provides structured major, minor, micro, and releaselevel values for inspecting the Python runtime.
2. 2
   platform.platform().startswith('Windows') is the decision point separating the Windows branch from the Unix-like branch.
3. 3
   The Windows source pattern uses HOMEDRIVE and HOMEPATH, while the Unix-like pattern uses HOME.
4. 4
   os.path.join() combines the selected directory with test.log using the platform-specific separator.
5. 5
   Logging levels filter messages, and logging.basicConfig() can use logging_file as the output path.