A couple of things: PCbuild/readme.txt Should be updated for the new release. PC/config.h VC++ 5.0 will not compile python20 unless "#include <basetsd.h>" is commented out. Trent? WITH_CYCLE_GC should be uncommented if we want to have GC enabled in the beta. PCbuild/python20.dsp Line endings seem to be incorrect. Someone probably edited the file on a Unix machine and munched things up. VC++ 5.0 likes DOS line endings otherwise it refuses to load the project. Also, I get a few warnings when compiling. One is about an /IZ (I think) option being ignored. There are a few other warnings as well which I didn't write down. Neil
A couple of things:
PCbuild/readme.txt
Should be updated for the new release.
Tim will do this.
PC/config.h
VC++ 5.0 will not compile python20 unless "#include <basetsd.h>" is commented out. Trent?
I'll leave this to Trent -- I don't know how to check for VC 5.0 vs. 6.0.
WITH_CYCLE_GC should be uncommented if we want to have GC enabled in the beta.
Done.
PCbuild/python20.dsp
Line endings seem to be incorrect. Someone probably edited the file on a Unix machine and munched things up. VC++ 5.0 likes DOS line endings otherwise it refuses to load the project.
There was one missing CR. Fixed now.
Also, I get a few warnings when compiling. One is about an /IZ (I think) option being ignored. There are a few other warnings as well which I didn't write down.
Probably 6.0 flags that 5.0 doesn't have. What can we do? --Guido van Rossum (home page: http://www.python.org/~guido/)
guido wrote:
PC/config.h
VC++ 5.0 will not compile python20 unless "#include <basetsd.h>" is commented out. Trent?
I'll leave this to Trent -- I don't know how to check for VC 5.0 vs. 6.0.
#if _MSC_VER >= 1200 VC 6.0 #else VC 5.0 or earlier #endif (we added a similar workaround to Python/thread_nt.c)
Also, I get a few warnings when compiling. One is about an /IZ (I think) option being ignored. There are a few other warnings as well which I didn't write down.
Probably 6.0 flags that 5.0 doesn't have. What can we do?
ignore it, for now. I remember seeing a few type warnings, but nothing critical. there's plenty of time to sort that out on the way to 2.0 final. </F>
Also, I get a few warnings when compiling. One is about an /IZ (I think) option being ignored. There are a few other warnings as well which I didn't write down.
Probably 6.0 flags that 5.0 doesn't have. What can we do?
This was probably "/ZI". "/ZI" means "symbolic information for edit-and-continue" and is only VC6. "/Zi" means "symbolic information", and is in _all_ VC versions. /ZI doesnt give us much for Python. Im my experience, changing Pythion binaries while debugging is cute, but pretty useless as often a .py file _also_ needs changing, and Python doesnt really support "edit-and-continue" in the same way. MSVC kindly bumps a "/Zi" option to "/ZI" automatically and silently when doing the VC5->VC6 updgrade So I can see no reason not to use "/Zi" for both. From the GUI, it should be obvious - its the symbolic debug option without edit-and-continue. Mark.
participants (4)
-
Fredrik Lundh -
Guido van Rossum -
Mark Hammond -
Neil Schemenauer