In article <[EMAIL PROTECTED]>, Alex Martelli <[EMAIL PROTECTED]> wrote: > >Hmmm - have you looked at Deitel, Deitel, Liperi, Wiedermann, "Python >how to program", chapters 18 (Process Management) and 19 >(Multithreading), pages 613-687? They seem to do a rather workmanlike >job -- of course, they can't do full justice to the subjects in 75 >pages; and if you don't want to buy a vast, costly 1300-pages tome for >the sake of those 75 pages, I can't really blame you, either.
Except that it's a really, really piss-poor book. That's an opinion which I believe you've agreed with previously. >And what about Norman Matloff's ><http://heather.cs.ucdavis.edu/~matloff/Python/PyThreads.pdf>, the first >google hit if you're looking for > python threads >? I haven't looked into it, but, again, without some specific >explanation of how it fails to meet your needs, it's hard to offer >alternatives. That's actually pretty good. -- Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ "19. A language that doesn't affect the way you think about programming, is not worth knowing." --Alan Perlis -- http://mail.python.org/mailman/listinfo/python-list
