[issue1706] Force WINVER 0x0500 (Windows 2000)
Christian Heimes added the comment: The macros don't restrain us to Win2k but they prevent us from using APIs which are not compatible with Windows 2000. It's a compile time option to conditionally exclude new features from the header files. #ifndef NTDDI_VERSION #define NTDDI_VERSION NTDDI_WIN2KSP4 #endif #ifndef WINVER #define WINVER 0x0500 #endif #ifndef _WIN32_WINNT #define _WIN32_WINNT WINVER #endif __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1706 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1704] possible bug in randint
Rich Marinaccio added the comment: To be clear, I am not using multi-threading in my particular module. I can't explain this behavior with my code alone. The issue is complicated by the fact that my module is called by Civ IV, and I have no idea what the game is doing behind the scenes. I also don't know exactly what happens when 'del myList[index]' is called. You would think that len(preshuffle) would have the same value for the randint call that it does for the print statement. I have an idea for another test I would like to try. This is my first issue that I've reported in Python. Would it help for me to attach the whole file? __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1704 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1704] possible bug in randint
Raymond Hettinger added the comment:
Attaching the whole file isn't a step in the right direction. The
preferred approach is to isolate the problem as tightly as possible.
This report is dubious because, I can't get the following to fail:
from random import seed, randint
seed('mystart')
while 1:
assert 0 = randint(0, 1452) = 1452
There is also no failure with:
preshuffle = [None] * 1453
while 1:
assert 0 = randint(0, len(preshuffle)-1) = 1452
Make sure that PWRand.randint() really does call randint() and not
randrange() and that it doesn't adjust the range of inputs.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1704
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1704] possible bug in randint
Rich Marinaccio added the comment: What was happening before was I was getting an index out of range error every so often, so then I put in the ValueError catch to see what was going on. I was surprised to see that randIndex was the same as len (preshuffle). I have some further catches in place now that might tell me more. It must have to do with deleting items from the list in the loop and not getting the right length from len immediately after, but then again I use this algorithm in several places in my module with no trouble, though with smaller lists. Go ahead and close this, and when I have more information I can open it some other time. This bug I'm seeing is extremely intermittant. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1704 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1706] Force WINVER 0x0500 (Windows 2000)
Martin v. Löwis added the comment: The macros don't restrain us to Win2k but they prevent us from using APIs which are not compatible with Windows 2000. --- That's what I meant by constrain/restrain: we can't use API that was added in XP directly. For functions, that is a good thing, because the binary wouldn't work on W2k. For enumeration values and structure definition, it's a bad thing, as we would need to duplicate them if we wanted to call the functions dyanmically that take such values. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1706 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1699] unconditional definiton of _BSD_SOURCE breaks builds with g++-4.3
Martin v. Löwis added the comment: I opted for conditionalizing it to OpenBSD; it was wrong on Linux, anyway, as _BSD_SOURCE has a different meaning there. Fixed in r59610 and r59611. -- resolution: - fixed status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1699 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1688] Incorrectly displayed non ascii characters in prompt using input() - Python 3.0a2
Vlastimil Brom added the comment: First sorry about a delayed response, but moreover, I fear, preparing a patch would be far beyond my programming competence; sorry about that. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1688 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
