Trent Nelson wrote: >> Where CPython beats IronPython is cross-platform capabilities. >> > > IronPython can use standard CPython modules though, right? I've dropped > my ipy.exe in C:\Python25 and it doesn't seem to have a problem with > things like os.path, which isn't available in IP (unless I'm doing > something brain dead). > You're right. If you add the standard library to your path then *most* of the pure Python modules 'just work'.
> >> On the other hand, Windows Forms (.NET) is better than any GUI toolkit >> I've seen. >> > > Out of interest, have you ever used Qt/PyQt? Qt blew MFC-style apps out > of the water in terms of developer friendliness a few years ago (which > is when I switched to it for all our C++ development, which is why I'm > somewhat biased). I'd be interested to hear from others in a similar > situation that can provide a comparison between Qt/PyQt and Windows > Forms .NET. > > I've never used Qt I'm afraid. Windows Forms seems like a generally sane and friendly API - even when called from Python. :-) Michael Foord http://www.voidspace.org.uk/ironpython/index.shtml _______________________________________________ Python-win32 mailing list Python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
