On Feb 7, 1:53 am, "S.Mohideen" <[EMAIL PROTECTED]> wrote: > Hi Folks, > > Python is praised about - me too. But at one instance it fails. It fails to > behave as a true multi-threaded application. That means utilizing all the > CPUs parallely in the SMP efficiently stays as a dream for a Python > Programmer. > > Discussion threads say its due to GIL - global interpreter lock. But nobody > has mentioned any alternative to that apart from suggestions like "Code it > in C" and POSH (http://poshmodule.sf.net). Is there any other way we can > make Python programs really multithreaded in real sense. > > Moin
Actually their are a *lot* more suggestions & discussions to be found. I myself move towards the "parallel processing is difficult. If you think it's easy then your either lucky or theorising. Whilst it would be nice to have threads==native threads for completeness sake, I'm quit happy to run concurrent communicating processes, as on my machines the OS helps me to see what's happening to the processes, and stops processes trampling over shared data". -Paddy. -- http://mail.python.org/mailman/listinfo/python-list
