On Sat, Nov 7, 2009 at 9:42 AM, Frank Wierzbicki <fwierzbi...@gmail.com> wrote: > On Sat, Nov 7, 2009 at 12:29 AM, Brian Quinlan <br...@sweetapp.com> wrote: > >> Right now multiprocessing is ahead of threading in terms of features. >> Pool.map() in particular is a pretty powerful idiom that has no equivalent >> in threading. > This is the area where I am most worried. Though multiprocessing is a > drop in replacement for threading, threading is not currently a drop > in replacement for multiprocessing. If multiprocessing doesn't make > sense for Jython and we need to tell our users that they should just > use threading, threading needs to do everything that multiprocessing > does... or maybe there needs to be a higher level package?
The only reason in my view that this is not the case is because no one has submitted a patch, myself included, it's been on my wish list for some time. There is nothing blocking that, AFAIK. _______________________________________________ stdlib-sig mailing list stdlib-sig@python.org http://mail.python.org/mailman/listinfo/stdlib-sig
