From 050391774a4d1233c392f4e113e51c5a44b3e0ba Mon Sep 17 00:00:00 2001 From: Brett Cannon Date: Mon, 28 Dec 2015 17:28:19 -0800 Subject: [PATCH] Issue #25930: Document that os.unlink and os.remove are *semantically* identical. Saying that the functions were identical confused some users who were upset when the functions were no longer simply the same function under different names. Thanks to Anthony Sottile for the bug report and Swati Jaiswal for the initial patch. --- Doc/library/os.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Doc/library/os.rst b/Doc/library/os.rst index c1193add13..373cafc525 100644 --- a/Doc/library/os.rst +++ b/Doc/library/os.rst @@ -1789,7 +1789,7 @@ features: be raised; on Unix, the directory entry is removed but the storage allocated to the file is not made available until the original file is no longer in use. - This function is identical to :func:`unlink`. + This function is semantically identical to :func:`unlink`. .. versionadded:: 3.3 The *dir_fd* argument. @@ -2452,10 +2452,10 @@ features: .. function:: unlink(path, *, dir_fd=None) - Remove (delete) the file *path*. This function is identical to - :func:`remove`; the ``unlink`` name is its traditional Unix - name. Please see the documentation for :func:`remove` for - further information. + Remove (delete) the file *path*. This function is semantically + identical to :func:`remove`; the ``unlink`` name is its + traditional Unix name. Please see the documentation for + :func:`remove` for further information. .. versionadded:: 3.3 The *dir_fd* parameter. -- 2.40.0