Andrew McNabb wrote:

If it made people feel better, maybe it should be called threading2
instead of multiprocessing.

I think that errs in the other direction, making it sound
like just another way of doing single-process threading,
which it's not.

Maybe "multicore" would help give the right impression?

(Still allows for networking -- nobody says all the cores
have to be on the same machine.:-)

--
Greg
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to