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 steve.dower
Recipients Luke.Dunstan, V.E.O, amaury.forgeotdarc, christian.heimes, eaducac, m_python, mloskot, mont29, pitrou, steve.dower, tim.golden, tim.peters, twasilczyk@spoon, vstinner
Date 2015-01-29.14:30:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1422541832.68.0.497241280966.issue17797@psf.upfronthosting.co.za>
In-reply-to
Content
This is fixed in VS2015 last time I tried it. I've proposed workarounds for this before, but it's never affected any official build do there's never been any traction. The fstat patch is normally the check that I use.

I don't know what Tomasz means that it's not fixed. Fixes like this don't magically appear in earlier VS versions, and while VS2015 does have the fix, it's not quite ready for production work.
History
Date User Action Args
2015-01-29 14:30:32steve.dowersetrecipients: + steve.dower, tim.peters, amaury.forgeotdarc, pitrou, vstinner, christian.heimes, tim.golden, eaducac, mloskot, V.E.O, m_python, mont29, Luke.Dunstan, twasilczyk@spoon
2015-01-29 14:30:32steve.dowersetmessageid: <1422541832.68.0.497241280966.issue17797@psf.upfronthosting.co.za>
2015-01-29 14:30:32steve.dowerlinkissue17797 messages
2015-01-29 14:30:32steve.dowercreate