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.

classification
Title: minor fix to make 1.6 compile under MSVC 5.0
Type: Stage:
Components: None Versions:
process
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: tmick Nosy List: effbot, tim.peters, tmick
Priority: normal Keywords: patch

Created on 2000-06-29 10:25 by effbot, last changed 2022-04-10 16:02 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
None effbot, 2000-06-29 10:25 None
Messages (5)
msg32935 - (view) Author: Fredrik Lundh (effbot) * (Python committer) Date: 2000-06-29 10:25
 
msg32936 - (view) Author: Tim Peters (tim.peters) * (Python committer) Date: 2000-06-30 00:32
Assigned this to Trent, since I didn't commit it and the next step is in Trent's court.
msg32937 - (view) Author: Trent Mick (tmick) (Python triager) Date: 2000-07-30 01:34
I came up with a cleaner solution, as promised to Guido. See:

http://sourceforge.net/patch/?func=detailpatch&patch_id=101010&group_id=5470
msg32938 - (view) Author: Fredrik Lundh (effbot) * (Python committer) Date: 2000-06-29 10:27
note that in the MSDN documentation, and in the 5.0
header files, the return value is declared to be an
"unsigned long".

maybe INT_PTR is just plain wrong?
msg32939 - (view) Author: Fredrik Lundh (effbot) * (Python committer) Date: 2000-06-29 17:29
committed (as a stopgap measure for 1.6b1).  hopefully,
trent will come up with a cleaner solution.
History
Date User Action Args
2022-04-10 16:02:02adminsetgithub: 32487
2000-06-29 10:25:44effbotcreate