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 jaraco
Recipients jaraco, theller
Date 2009-01-31.21:33:17
SpamBayes Score 6.6544235e-06
Marked as misclassified No
Message-id <1233437603.32.0.991645388729.issue5119@psf.upfronthosting.co.za>
In-reply-to
Content
After putting together a more simple example without externalities, I'm
unable to continue to assert the discrepancy between 32 and 64-bit
Windows, although I do still see where narrow character strings are
treated as wide character buffers.

See the attached script that demonstrates the issue (on Python 2.5 and
Python 2.6 regardless of word size).

Now the inconsistency seems to only lie with the WNetAddConnection2W
function and not the MessageBoxW function, both of which take LPCTSTR
parameters (at least according to the documentation).

Perhaps this is a non-issue, but I'd be interested to know why the
WNetAddConnection2W example works in 32-bit but not 64-bit.  Could it be
the 32-bit WNetAddConnection2W actually attempts to handle the buffer as
both wide and narrow, but MessageBoxW takes it at face value?
History
Date User Action Args
2009-01-31 21:33:23jaracosetrecipients: + jaraco, theller
2009-01-31 21:33:23jaracosetmessageid: <1233437603.32.0.991645388729.issue5119@psf.upfronthosting.co.za>
2009-01-31 21:33:19jaracolinkissue5119 messages
2009-01-31 21:33:18jaracocreate