Hi all, FYI - Ive just finished checking into CVS all the changes necessary for Python 2.0. So if you update the complete Python tree from sourceforge and the Win32 extensions trees from pythonpros, you should get successful builds of everything. I recommend that you seek-and-destroy Py*16* on your machine - this will ensure that if you have missed any extension modules, you get a nice "Python16.dll not found", rather than the thread-state crash that happens if that DLL does indeed still exist. Mark.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4