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 jniehof
Recipients eric.araujo, hynek, jniehof, r.david.murray, tarek
Date 2011-08-23.13:41:38
SpamBayes Score 0.0409802
Marked as misclassified No
Message-id <1314106898.72.0.554053448575.issue9993@psf.upfronthosting.co.za>
In-reply-to
Content
Éric: I think copying a relative symlink should also be relative, and that's the behaviour of this patch. That was the use case that tripped me up with the original behaviour of shutil.move: a relative symlink which was dangling in its original location, but not once moved. (This was, believe it or not, intentional design....)

This is also the behaviour when src and dst are on the same filesystem. Basically my intention was to remove the distinction between "same filesystem" and "different filesystem."
History
Date User Action Args
2011-08-23 13:41:38jniehofsetrecipients: + jniehof, tarek, eric.araujo, r.david.murray, hynek
2011-08-23 13:41:38jniehofsetmessageid: <1314106898.72.0.554053448575.issue9993@psf.upfronthosting.co.za>
2011-08-23 13:41:38jniehoflinkissue9993 messages
2011-08-23 13:41:38jniehofcreate