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 SilentGhost
Recipients SilentGhost, docs@python, serhiy.storchaka, skeo
Date 2019-05-23.07:35:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1558596901.94.0.723877153718.issue37019@roundup.psfhosted.org>
In-reply-to
Content
This would be backward incompatible change. I just wanted to point out that the symlink was only broken because the file did not exist, and one might want to legitimately create a link relative to the target's location. I'd imagine creating a link in the same directory is one such example. I think the issue you're raising can be addressed in documentation, by making clear that the relative link will be relative to target. This is already done in the given example for symlink_to, but could be improved using a target in subdirectory and a clarifying note.

The relative_to issue does indeed deserve a separate issue (if there isn't one already).
History
Date User Action Args
2019-05-23 07:35:01SilentGhostsetrecipients: + SilentGhost, docs@python, serhiy.storchaka, skeo
2019-05-23 07:35:01SilentGhostsetmessageid: <1558596901.94.0.723877153718.issue37019@roundup.psfhosted.org>
2019-05-23 07:35:01SilentGhostlinkissue37019 messages
2019-05-23 07:35:01SilentGhostcreate