This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author barneygale
Recipients barneygale, docs@python
Date 2021-01-22.04:24:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1611289460.25.0.942447627462.issue42999@roundup.psfhosted.org>
In-reply-to
Content
Compare the documentation of `symlink_to()` and `link_to()`:

.. method:: Path.symlink_to(target, target_is_directory=False)
    Make this path a symbolic link to *target*.

.. method:: Path.link_to(target)
    Create a hard link pointing to a path named *target*.

In fact, `link_to()` does something like:

    Make *target* a hard link to this path.

Which is unexpected given the naming and inconsistency with `symlink_to()`, but it's the way the current implementation works, and so the documentation should reflect that.

Adding a replacement `hardlink_to()` function is covered here in bpo-39950.
History
Date User Action Args
2021-01-22 04:24:20barneygalesetrecipients: + barneygale, docs@python
2021-01-22 04:24:20barneygalesetmessageid: <1611289460.25.0.942447627462.issue42999@roundup.psfhosted.org>
2021-01-22 04:24:20barneygalelinkissue42999 messages
2021-01-22 04:24:20barneygalecreate