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 pitrou
Recipients brian.curtin, db3l, pitrou, tim.golden
Date 2010-09-21.00:04:12
SpamBayes Score 8.23065e-07
Marked as misclassified No
Message-id <1285027456.78.0.828515138477.issue9908@psf.upfronthosting.co.za>
In-reply-to
Content
Under Windows 7, there is another path in posixmodule.c for stat() (because of the link dereferencing feature, it seems). This path fails for the bytes version. It turns out that GetFinalPathNameByHandleA returns a value which is one byte too small (while GetFinalPathNameByHandleW returns the expected value). The MSDN doc (*) seems to mention it although with a strange wording:

    “Windows Server 2008 and Windows Vista:  For the ANSI version of this function, GetFinalPathNameByHandleA, the return value includes the size of the terminating null character.”

(*) http://msdn.microsoft.com/en-us/library/aa364962%28VS.85%29.aspx

The net result is that, when we give 'buf_size+1' to the second GetFinalPathNameByHandleA() call after 'buf_size' was returned by the first call, the buffer is still not big enough and it doesn't get filled. The subsequent call to win32_lstat() is done with a bogus path and fails with "[Error 2]: the system cannot find the file specified".

Here is a patch fixing this and also harmonizing win32_stat() and win32_stat_w(). I've added a test, although additional tests for bytes symlinks would probably be deserved. Please review.

PS: the context is:
http://mail.python.org/pipermail/python-dev/2010-September/103860.html
History
Date User Action Args
2010-09-21 00:04:17pitrousetrecipients: + pitrou, db3l, tim.golden, brian.curtin
2010-09-21 00:04:16pitrousetmessageid: <1285027456.78.0.828515138477.issue9908@psf.upfronthosting.co.za>
2010-09-21 00:04:15pitroulinkissue9908 messages
2010-09-21 00:04:14pitroucreate