Tim Roberts wrote: > happybrowndog wrote: > >> I've had Mark's Python Programming on Win32 book for 6 years now, and >> it's been a constant source of information and a joy to read and possess. >> >> Windows has added a lot since the book hit the shelves, with the >> maturation of .Net, winforms and other application technologies, and a >> "new" OS. There's still the old way of doing things with COM, etc. The >> Ctypes package has also fleshed out to be very useful on Windows. Then >> there's IronPython, and Python for .Net. >> >> > > Well, there's an interesting issue here. Much of the new stuff you have > mentioned has nothing to do with the Python that we know and love. .NET > and winforms (which is part of .NET) requires managed code, and that > means IronPython. IronPython is NOT the same as Python; although the > language is the same, the library and the idiomatic usage are so very > different that it's difficult for one person to be competent in both. > >
Hmmm... that hasn't been my experience. Programming IronPython with idiomatic Python works very well. Michael http://www.manning.com/foord > Indeed, for things that are not .NET, Mark's book is still pretty much > current. > > Perhaps we'll get a book on IronPython to make it a little more > approachable for us CPython users. > > _______________________________________________ python-win32 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-win32
