I have managed to get all our critical python code up and running under 2.0b1#4, around 15,000 lines. We use win32com and wxPython extensions. The code drive SourceSafe and includes a Web server that schedules builds for us. The only problem I encounted was the problem of mixing string and unicode types. Using the smtplib I was passing in a unicode type as the body of the message. The send() call hangs. I use encode() and all is well. Is this a user error in the use of smtplib or a bug? I found that I had a lot of unicode floating around from win32com that I was passing into wxPython. It checks for string and raises exceptions. More use of encode() and we are up and running. Is this what you expected when you added unicode? Barry
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