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 random832
Recipients loewis, palaviv, random832
Date 2016-04-16.15:47:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Wouldn't the "symlink infinite loop" case be better handled by making it track where it's already been? This can be done by inode and dev number on Unix; I'm not sure what equivalent exists on Windows (though symlinks are uncommon on Windows) but you could fall back on realpath.
Date User Action Args
2016-04-16 15:47:52random832setrecipients: + random832, loewis, palaviv
2016-04-16 15:47:51random832setmessageid: <>
2016-04-16 15:47:51random832linkissue26781 messages
2016-04-16 15:47:51random832create