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 techtonik
Recipients Trundle, draghuram, eric.araujo, giampaolo.rodola, neologix, pitrou, r.david.murray, tarek, techtonik, vstinner
Date 2011-12-23.17:26:02
SpamBayes Score 3.2597782e-07
Marked as misclassified No
Message-id <CAPkN8x+Ro167g3Bact4RaPjPMKhKcGkcMrbcGQ5usqNG6PH_qg@mail.gmail.com>
In-reply-to <1324657855.68.0.175662338942.issue8828@psf.upfronthosting.co.za>
Content
2011/12/23 Charles-François Natali <report@bugs.python.org>
>
> > One of the Python advantages is providing predictable cross-platform
> > behavior. If we can't introduce nice API without BC break, it is not
> > a reason to introduce ulgy API.
>
> We cannot make rename() overwrite existing files by default (on Windows).
> It's out of question, too much code might rely on this, and this may very
> well introduce security flaws.
> If you're concerned with the semantics difference between platforms, well,
> there's not much we can do about it now. Java behaves in the same way, for
> example.
>

I propose quite the opposite. rename() should not overwrite existing files
by default.
History
Date User Action Args
2011-12-23 17:26:03techtoniksetrecipients: + techtonik, pitrou, vstinner, draghuram, giampaolo.rodola, tarek, eric.araujo, r.david.murray, Trundle, neologix
2011-12-23 17:26:03techtoniklinkissue8828 messages
2011-12-23 17:26:02techtonikcreate