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 thehesiod
Recipients elias, eric.araujo, hynek, ncoghlan, r.david.murray, tarek, thehesiod
Date 2014-03-15.09:01:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CALEOg0Cgr_-7z8Gf9cA3eY3CgW=QDteFago-1JU710txwr+14A@mail.gmail.com>
In-reply-to <1394849754.21.0.295757517143.issue20849@psf.upfronthosting.co.za>
Content
Ya. The original request I think is ok because by allowing that flag it
will replace files and dirs.
On Mar 14, 2014 7:15 PM, "R. David Murray" <report@bugs.python.org> wrote:

>
> R. David Murray added the comment:
>
> I don't know what "the method already allows for existing files" means.
>  Since the target directory can't exist, there can be no existing files.
>
> In unix, this kind of capability is provided by a combination of shell
> globbing and 'cp -r', and by default it does replace existing files.  So it
> would be reasonable for exists_ok to mean exactly that: replace anything
> that currently exists, if it does.
>
> I think that would be a reasonable API, but the implementation isn't as
> simple as just passing through the exists_ok flag to makedirs.
>
> I do not think that *just* making it OK for the destination directory to
> exist would be a good API.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue20849>
> _______________________________________
>
History
Date User Action Args
2014-03-15 09:01:29thehesiodsetrecipients: + thehesiod, ncoghlan, tarek, eric.araujo, r.david.murray, elias, hynek
2014-03-15 09:01:29thehesiodlinkissue20849 messages
2014-03-15 09:01:29thehesiodcreate