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 kinow
Recipients QueenSvetlana, eryksun, kinow, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-12-02.01:53:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1575251591.29.0.421613269077.issue38868@roundup.psfhosted.org>
In-reply-to
Content
I think eryksun is correct. Reproduced it locally. Setting to read-only initially did not raise the issue, but then as administrator I removed the inherited permissions and set it to read-only for my user, then it raised the exact same WinError 5 Permission Error.

With the extra code to remove the readonly attribute, the directory was successfully deleted.

>It does so as an accident of history, not because it's justified

I think it would be easier for users if this attribute was not copied, especially as it looks like other attributes are not being copied (on Win). That would remove the need of this extra code when using Windows.
History
Date User Action Args
2019-12-02 01:53:11kinowsetrecipients: + kinow, paul.moore, tim.golden, zach.ware, eryksun, steve.dower, QueenSvetlana
2019-12-02 01:53:11kinowsetmessageid: <1575251591.29.0.421613269077.issue38868@roundup.psfhosted.org>
2019-12-02 01:53:11kinowlinkissue38868 messages
2019-12-02 01:53:11kinowcreate