gladman added the comment: On 30/09/2013 12:39, STINNER Victor wrote: > > STINNER Victor added the comment: > >> I am surprised that this bug still exists as it is not far off two years old >> now. > > You should report the bug to Microsoft who distributes a buggy C runtime > library. > > ---------- > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <http://bugs.python.org/issue13674> > _______________________________________ >
Thank you for your suggestion. But, given that this bug has been present for some two years, I would hope that Python developers would have already done what you suggest and this leads me to doubt that any approach that I made to Microsoft would achieve any practical benefit. In practice it is pretty well always necessary in building applications on top of widely used compilers and libraries to have to workaround the many bugs that they contain. Since there is evidently no workaround for this issue in the Python 3.3.2 code, I have to assume that one is not considered to be necessary, presumably because Microsoft has fixed (or intends to fix) this issue. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13674> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
