[issue39925] `pathlib.Path.link_to()` has the wrong argument order

Eric V. Smith added the comment: Agreed it's a duplicate, so I'm closing this. For any further discussion, please use issue39291, or better yet, do as it suggests and discuss this on python-dev. -- resolution: -> duplicate stage: patch review -> resolved status: open -> closed super

[issue39925] `pathlib.Path.link_to()` has the wrong argument order

Karthikeyan Singaravelan added the comment: This seems to be a duplicate of issue39291. -- nosy: +pitrou, xtreak ___ Python tracker ___ ___

[issue39925] `pathlib.Path.link_to()` has the wrong argument order

Change by Barney Gale : -- keywords: +patch pull_requests: +18264 stage: -> patch review pull_request: https://github.com/python/cpython/pull/18909 ___ Python tracker ___

[issue39925] `pathlib.Path.link_to()` has the wrong argument order

Barney Gale added the comment: I'm not sure how it can be fixed on the documentation side - it's difficult to explain that `a.link_to(b)` creates a link from B to A, and not vice-versa. We could introduce a new method that does the right thing? `Path.hardlink_to()`? -- _

[issue39925] `pathlib.Path.link_to()` has the wrong argument order

Eric V. Smith added the comment: I think it's too late to change this. Is this a documentation issue? -- nosy: +eric.smith ___ Python tracker ___ _

[issue39925] `pathlib.Path.link_to()` has the wrong argument order

New submission from Barney Gale : `mylink.symlink_to(target)` and `mylink.link_to(target)` should both create a link (soft or hard) at *mylink* that points to *target*. But `link_to()` does the opposite - it creates *target* and points it towards *mylink*. Correct behaviour from `symlink_to(