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 plakhotich
Recipients martin.panter, paul.moore, plakhotich, r.david.murray, steve.dower, tim.golden, zach.ware
Date 2015-11-09.23:13:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
You mean msg254341? As I mentioned recently, it still will raise an exception
in case of EROFS, ENOSPC and possibly other values, which, as in the case
with Windows, can be quite unexpected depending on platform and circumstances.

Of course there is no practical sense to continue when, for example, FS is
read-only (EROFS), but I think makedirs must be predictable: it should
first check and only then try to create, as it stated in the docstring.
When exist_ok=True and directory really exists, a user doesn't expect any
exceptions from the internally used mkdir, because it simply shouldn't be
called in this case.

By the way, why 3.2 and 3.3 were removed from the list? exist_ok was introduced in 3.2.
Date User Action Args
2015-11-09 23:13:14plakhotichsetrecipients: + plakhotich, paul.moore, tim.golden, r.david.murray, martin.panter, zach.ware, steve.dower
2015-11-09 23:13:14plakhotichsetmessageid: <>
2015-11-09 23:13:14plakhotichlinkissue25583 messages
2015-11-09 23:13:14plakhotichcreate