Even I, as a strong advocate for it's inclusion think I should finish the PEP and outline all of the questions/issues that may come out of it. On Thu, Mar 20, 2008 at 1:37 PM, Facundo Batista <facundobatista at gmail.com> wrote: > 2008/3/20, Andrew McNabb <amcnabb at mcnabbs.org>: > > > > Since we officially encourage people to spawn processes instead of > > threads, I think that this would be a great idea. The processing module > > has a similar API to threading. It's easy to use, works well, and most > > importantly, gives us some place to point people to when they complain > > about the GIL. > > I'm +1 to include the processing module in the stdlib. > > just avoid confussions, with these libraries with alike names, I'm > meaning this [1] module, the one that emulates the semantics of > threading module. > > Does anybody has strong reasons for this module to not get included? > > Regards, > > [1] http://pypi.python.org/pypi/processing > > -- > . Facundo > > Blog: http://www.taniquetil.com.ar/plog/ > PyAr: http://www.python.org/ar/ > > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/jnoller%40gmail.com >
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4