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 eryksun
Recipients eryksun, paul.moore, stephan, steve.dower, tim.golden, vstinner, zach.ware
Date 2016-10-04.14:00:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
3.3 added os.replace, which on Windows entailed a switch from calling MoveFile to MoveFileEx in order to specify the MOVEFILE_REPLACE_EXISTING flag. However, not passing the MOVEFILE_COPY_ALLOWED broke compatibility with os.rename on Windows for versions prior to 3.3. I don't know whether or not this was discussed as an intentional breaking change in order to align the behavior with POSIX rename(). The change seems reasonable to me, plus at this point I don't think much can be done other than to add a note to the docs that the behavior changed in 3.3.
Date User Action Args
2016-10-04 14:00:10eryksunsetrecipients: + eryksun, paul.moore, vstinner, tim.golden, zach.ware, steve.dower, stephan
2016-10-04 14:00:10eryksunsetmessageid: <>
2016-10-04 14:00:10eryksunlinkissue28356 messages
2016-10-04 14:00:10eryksuncreate