https://nalar.dev/tags/pathlib/ Recent content in Pathlib on Nalar Hugo en-us Tue, 08 Sep 2026 00:00:00 +0700 https://nalar.dev/copy-and-move-paths-with-pathlib-in-python-3-14/ Tue, 08 Sep 2026 00:00:00 +0700 https://nalar.dev/copy-and-move-paths-with-pathlib-in-python-3-14/ <p>Python 3.14 adds high-level copy and move operations directly to <code>pathlib.Path</code>. <code>Path.copy()</code>, <code>Path.copy_into()</code>, <code>Path.move()</code>, and <code>Path.move_into()</code> make many filesystem workflows easier to express without switching between <code>pathlib</code>, <code>shutil</code>, and <code>os</code> for basic operations.</p> <p>The convenience is useful, but filesystem mutations still need explicit policy. Overwrites, symbolic links, metadata, cross-filesystem moves, partial failure, and concurrent changes can all affect correctness.</p> <h2 id="the-four-new-operations">The four new operations</h2> <p>Use <code>copy()</code> when the destination path itself is known:</p> https://nalar.dev/walk-directory-trees-with-pathlib-path-walk/ Tue, 08 Sep 2026 00:00:00 +0700 https://nalar.dev/walk-directory-trees-with-pathlib-path-walk/ <p>Python 3.12 added <code>pathlib.Path.walk()</code>, bringing directory-tree traversal directly to <code>Path</code> objects. It fills the same broad role as <code>os.walk()</code>, but keeping traversal and path manipulation in <code>pathlib</code> can make filesystem code easier to read.</p> <p>Walking a tree is deceptively simple, though. Production code needs to decide which subtrees to enter, what to do with unreadable directories, whether symbolic links should be followed, and whether the filesystem may change during traversal.</p>