[issue21876] os.rename(src, dst) does nothing when src and dst files are hard-linked
Aaron Swan added the comment: At any rate, it is a bit of a nuisance that files remain present when the intent was to move them. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21876 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21876] os.rename(src, dst) does nothing when src and dst files are hard-linked
New submission from Aaron Swan: On Linux Red Hat os.rename(src,dst) does nothing when src and dst files are hard-linked. It seems like the expected behavior would be the removal of the src file. This would be in keeping with the documentation that states: On Unix, if dst exists and is a file, it will be replaced silently if the user has permission. -- messages: 221699 nosy: Aaron.Swan priority: normal severity: normal status: open title: os.rename(src,dst) does nothing when src and dst files are hard-linked type: behavior versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21876 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21876] os.rename(src, dst) does nothing when src and dst files are hard-linked
Aaron Swan added the comment: Although using the mv command *does* remove the src file on red hat linux, I can accept that the POSIX requirement that the source *must* be removed might not apply if source is the same as the destination file. It would be nice if the behavior was consistent, but I think the POSIX requirements are somewhat up for interpretation in this case. The documentation should probably be updated at the least. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21876 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
