Message 58356 - Python tracker

➜

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	gvanrossum
Recipients	facundobatista, gvanrossum, init
Date	2007-12-10.18:15:05
SpamBayes Score	0.32181063
Marked as misclassified	No
Message-id	<1197310506.24.0.544440963376.issue1577@psf.upfronthosting.co.za>
In-reply-to

Content
We should first decide what should happen. While for command line tools "mv FILE DIR" is established syntax for "mv FILE DIR/`basename FILE`", I'm not at all sure that shutil.move(src, dst) should do the same. I think it should be closer to the UNIX os.rename() semantics which promises that src replaces dst. If dst is an empty dir, it is removed using rmdir(); if it is a non-empty dir, the removal fails and hence the move fails. I think this is what shutil.move() should do too. (Even if it can't make the atomicity promises that UNIX makes.)

We should first decide what should happen.  While for command line tools
"mv FILE DIR" is established syntax for "mv FILE DIR/`basename FILE`",
I'm not at all sure that shutil.move(src, dst) should do the same.  I
think it should be closer to the UNIX os.rename() semantics which
promises that src *replaces* dst.  If dst is an empty dir, it is removed
using rmdir(); if it is a non-empty dir, the removal fails and hence the
move fails.  I think this is what shutil.move() should do too.  (Even if
it can't make the atomicity promises that UNIX makes.)

History
Date	User	Action	Args
2007-12-10 18:15:06	gvanrossum	set	spambayes_score: 0.321811 -> 0.32181063 recipients: + gvanrossum, facundobatista, init
2007-12-10 18:15:06	gvanrossum	set	spambayes_score: 0.321811 -> 0.321811 messageid: <1197310506.24.0.544440963376.issue1577@psf.upfronthosting.co.za>
2007-12-10 18:15:06	gvanrossum	link	issue1577 messages
2007-12-10 18:15:05	gvanrossum	create