Barry Scott wrote:
I recursive grep'ed and missed this ref. However I did read this in
README.TXT:
Building on non-UNIX systems
For Windows (2000/NT/ME/98/95), assuming you have MS VC++ 6.0, the
project files are in PCbuild, the workspace is pcbuild.dsw. See
Barry Scott [EMAIL PROTECTED] writes:
I recursive grep'ed and missed this ref. However I did read this in
README.TXT:
The top-level README file is hilariously out-of-date, in some ways. I
meant to do something about this before 2.4 final, but didn't get
around to it...
Cheers,
mwh
--
Hi,
On Fri, Dec 24, 2004 at 12:17:49AM +, Barry Scott wrote:
I recursive grep'ed and missed this ref. However I did read this in
README.TXT:
The extending and embedding tutorial is similarily out-of-date.
Armin
___
Python-Dev mailing list
Armin Rigo [EMAIL PROTECTED] writes:
Hi,
On Fri, Dec 24, 2004 at 12:17:49AM +, Barry Scott wrote:
I recursive grep'ed and missed this ref. However I did read this in
README.TXT:
The extending and embedding tutorial is similarily out-of-date.
Well, I've half re-written that (the
I see that, as expected, windows python 2.4 was built with MSVC 7.1
rather then msvc 6.0.
It seems that I can build extensions with msvc 6.0 that work with the
python 2.4 windows
binary kit.
Is this safe?
I recall warning a while ago about mixing msvc 6.0 and msvc 7.1 runtime
DLL's. Is this
Barry Scott wrote:
It seems that I can build extensions with msvc 6.0 that work with the
python 2.4 windows
binary kit.
Is this safe?
No, it isn't. This emerges as a Python 2.4 FAQ.
I recall warning a while ago about mixing msvc 6.0 and msvc 7.1 runtime
DLL's. Is this
an issue with python 2.4?
On Dec 23, 2004, at 23:12, Martin v. Löwis wrote:
Barry Scott wrote:
It seems that I can build extensions with msvc 6.0 that work with the
python 2.4 windows
binary kit.
Is this safe?
No, it isn't. This emerges as a Python 2.4 FAQ.
I recall warning a while ago about mixing msvc 6.0 and msvc 7.1
