File Paths: Relative, Absolute and Resolved Locations

A script is stored in one directory but launched while the terminal is in another. A relative report path may refer to the launch directory, not automatically to the script’s directory.

A relative path is interpreted against a base location. An absolute path starts from a platform’s filesystem root. Path tools build and inspect paths according to the platform’s rules.

Python open with a relative path uses the process’s current working directory. That may differ from the script directory. If a program needs script-relative files, choose that base explicitly rather than depending on launch context.

Roots and separators differ across platforms. Python pathlib and Node path APIs provide platform-aware operations. A joined path can still be missing or forbidden; constructing it performs no read.

Before starting, review real file operations. These examples use JavaScript; other languages can use different syntax and rules.

This complete Python 3 example uses pathlib. It creates no file. join through / combines path parts according to the platform.

from pathlib import Path

report = Path('school') / 'reports' / 'marks.txt'
print(report.name)
print(report.is_absolute())
print(Path.cwd().is_absolute())

Expected output: marks.txt, False and True. cwd reports the current working directory. Its exact location depends on how the program was launched.

This JavaScript URL example illustrates base-relative versus root-relative selection. The first name resolves inside /reports/ while the rooted name starts at /.

It accesses no filesystem and does not claim URL rules equal operating-system path rules. The actual path API is shown before this analogy.

For a Python 3 script saved as path_report.py, __file__ identifies the script path. This program writes an exercise report beside that script, not at an arbitrary terminal launch directory.

from pathlib import Path

base = Path(__file__).resolve().parent
report = base / 'exercise-report.txt'
report.write_text('Maya: 75', encoding='utf-8')
print(report.read_text(encoding='utf-8'))

Expected output: Maya: 75. Run this only in a disposable directory where replacing exercise-report.txt is intended. Interactive environments may not define __file__.

In the URL analogy, resolve ../marks.txt from /reports/daily/ and state which directory is selected.

Joining arbitrary user input does not guarantee containment: parent segments, absolute paths and symbolic links can affect the final target. Define allowed locations and enforce them using the actual environment’s path and access rules.

Normalization does not establish that a file exists or that the current user is authorized to read it. Filesystem paths are not URL strings; encoding, roots and separators have different detailed rules.

For the language or tool rules used here, see Python filesystem paths.

Relative paths depend on a base; absolute paths name a rooted location. Use real path tools, choose launch-relative or script-relative behavior deliberately, and keep authorization separate from normalization.

Connect this idea with actual access outcomes and project boundaries.