<div>Hi Mark<br><br></div>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Pedantic side-note: best I can tell, all the compilers are x86 binaries, so<br>even on a 64bit OS, we are still cross-compiling :)</blockquote>
<div> </div>
<div>You are of course correct, I should have said I am developing on a 64 bit machine.</div>
<div> </div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Grab the source .zip for build 211 now it is fresh, but otherwise, a work<br>around would be to update CVS from home, then run "setup.py sdist" and move<br>
the resulting .zip file to work.</blockquote>
<div> </div>
<div>Spotted that and thanks for the setup tip, I also spotted there is a 2.6 64 bit build this seemed to install ok with python 2.6 ok, so I will probably just use that. What compiler was used for this package?<br></div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I agree for 32bit builds, but IMO the 64 bit builds are somewhat different -<br>the lack of 64bit binaries for most python 2.5 extensions implies to me that<br>
x64 on 2.6 isn't any risker; particularly when talking about 2.5 builds<br>using an "unsupported" compiler. From pywin32's POV, I'm quite certain more<br>people are testing x64 using 2.6 builds than 2.5.</blockquote>
<div> </div>
<div>Point duly noted, I will examine 2.6 instead then and see how it goes. SO long as I can get all the tests running without any problems then I will be happy, and by the time we deploy it looks like 2.6 should be pretty much ready.</div>
<div> </div>
<div>Thanks again,</div>
<div> </div>
<div>Hanni</div>
<div> </div></div>