PEP 371: Addition of pyprocessing (as multiprocessing) accepted!

June 5th, 2008 § 11 comments

Per Guido:

I’ve accepted your PEP. I think it still needs some clean-up and
per­haps clar­i­fi­ca­tion of the agree­ment reached about API style, but
there is noth­ing now that keeps you from imple­ment­ing it! Hope­fully
you’ll make the beta release early next week.

–Guido

Woop woop woop.

  • Brett

    Damn, now I am going to have to care about mul­ti­pro­cess­ing in my Python apps. =)

  • http://blog.gumuz.nl/ gumuz

    cool, good luck!

  • dpinkney

    DING! Nice.

  • Paddy3118

    Hmmm,
    Maybe wide finder 2 + Py3K + pypro­cess­ing?
    (http://www.tbray.org/ongoing/When/200x/2008/05/…)

    - Paddy

  • http://www.gamr7.com LBar­ret

    Good ! good ! good !

  • jnoller

    Yeah right after I fig­ure out how to get it into trunk. Has any­one ever men­tioned that get­ting C exten­sions in there is uh, obtuse? :)

  • jnoller

    omg +1 sword of concurrency

  • jnoller

    I’ve been tempted to try to hit up that, but given I’m bogged down with Pymag + Python Core + Work + Other stuff, I don’t think I’ll be vol­un­teer­ing for much more soon :)

  • jnoller

    I thought so!

  • http://anderswallin.net Anders

    I just tried this for the first time and wrote a mul­ti­pro­cess­ing pys­tones bench­mark. Check it out here:
    http://www.anderswallin.net/2008/06/multiproces…

    great work!

  • http://anderswallin.net Anders

    I just tried this for the first time and wrote a mul­ti­pro­cess­ing pys­tones bench­mark. Check it out here:
    http://www.anderswallin.net/2008/06/multiproces…

    great work!

What's this?

You are currently reading PEP 371: Addition of pyprocessing (as multiprocessing) accepted! at jessenoller.com.

meta