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 tim.golden
Recipients ivan.radic, r.david.murray, tim.golden, zach.ware
Date 2013-11-18.19:32:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <528A6B71.1070305@timgolden.me.uk>
In-reply-to <1384802653.85.0.680450566707.issue19643@psf.upfronthosting.co.za>
Content
TBH I'm still fairly -0 and edging towards -0.5. If we didn't already 
have two keyword args I might be convinced towards a jfdi=True flag. 
But, as the OP described, the current params already allow for a 
workaround of sorts and another param of the semantics we're discussing 
would surely just be confusing?

(Or you could just "preprocess" on Windows, eg attrib -r /s)
History
Date User Action Args
2013-11-18 19:32:45tim.goldensetrecipients: + tim.golden, r.david.murray, zach.ware, ivan.radic
2013-11-18 19:32:45tim.goldenlinkissue19643 messages
2013-11-18 19:32:45tim.goldencreate