Python for Win32 Extensions for 1.6 and 2.0b1

Robin Becker robin at jessikat.fsnet.co.uk
Fri Sep 8 13:05:22 CEST 2000


In article <3n_t5.33829$Xg.235495 at news-server.bigpond.net.au>, Mark
Hammond <MarkH at ActiveState.com> writes
>Hi all,
>    There is a new release of the win32all package for Python 1.6
>final, and 2.0b1.
>
>However, these are no longer being released from the usual place.  I
>am able to use the resources of my employer to move new releases to
>http://www.activestate.com/Products/ActivePython/win32all.html.
>
>At this site you will find information about the new release,
>including win32all-133.exe for Python 1.6, and win32all-134.exe for
>Python 2.0.  (actually, 134 is not linked yet - it is at
>www.activestate.com/download/ActivePython/windows/win32all/win32all-13
>4.exe)
>
>My starship page at http://starship.python.net/crew/mhammond has been
>updated to reflect this change.
>
>Please let me know of any problems..
>
>Mark.
Win95 OSR2: 
I get this running 134 with 2.0b1; I had to make one slight change to
get win32ui.pyd to behave OK (ie I compiled without the reference to
ToUnicodeEx), but I don't think that's the problem here. I reckon it
must be a late change in the thread module which I saw stuffed in a few
days ago!

C:\Python20\win32com\test>..\..\python testall.py
The Exchange Server tests can not be run...
testStreams test generated 9 lines of output
Fatal Python error: PyThreadState_Get: no current thread

abnormal program termination

C:\Python20\win32com\test>

-- 
Robin Becker



More information about the Python-list mailing list