> I just ran the installer. Under Help - About it claims to be build
> 210.9!
Bugger - that was a breakdown in my packaging process :(
pywin32.version.txt still has 210.9 in it, but you certainly have build 211
there. My apologies - you can edit this .txt file if it worries you.
Cheers,
Mark
_
Mark Hammond wrote:
Hi all,
I've finally released pywin32 build 211!
These days, it almost goes without saying that Roger Upole again contributed
significant changes, and various other people also contributed bits and
pieces - the full change notes are at:
https://sourceforge.net/project/shown
> Firstly, I am currently using VS2005 as I am compiling Python-2.5.2
because
> I was going for the most stable python. Everyone here seems to think I
should
> be using 2.6, as far as I can tell this is still in alpha and I am not
convinced
> of the wisdom of using an alpha testing system for pro
Hi!
I've finally released pywin32 build 211!
Super mega very great new!
To celebrate that, I invite you to aperitif, today, at midday.
It's here:
http://maps.google.com/?ie=UTF8&om=1&ll=44.384614,4.639181&spn=0.013801,0.045877&t=h&z=15at
very soon;o)Michel Claveau
___
Thanks for some of the advice,
A little background so my questions make sense.
This deployment is for a mission critical application. I am migrating it
from python-2.4 to 2.5 also changing the code which uses numarray/numeric to
use numpy which is one of the main parts of the move (I thought), th
Hi all,
I've finally released pywin32 build 211!
These days, it almost goes without saying that Roger Upole again contributed
significant changes, and various other people also contributed bits and
pieces - the full change notes are at:
https://sourceforge.net/project/shownotes.php?release_id=60
