Getting Processing into the stdlib

May 15th, 2008 § 6 comments

I shot an email out to Python-Dev ear­lier this week ask­ing for comments/questions regard­ing my push to get the Pro­cess­ing into the stan­dard library. There’s been some decent dis­cus­sion about tar­get releases and other meta-issues around get­ting it in.

Right now, it looks like I am going to try to tar­get 2.7 and 3.1 — this makes sense for a few reasons.

  • First, the PEP dead­line was uh, a year ago for 2.6 and 3.0
  • There’s some cleanup on the mod­ule which needs to be done
  • There might be some renam­ing requirements
  • Need to talk to R. about a 1.0 release
  • Need to chunk out some time to con­vert the tests to unit test format.

That all being said — it doesn’t look unfea­si­ble to accom­plish — and the response both on list and to me pri­vately has been 95% +1 and 5% -.5 and –1 — the pos­i­tive response really does make me feel that this is the right approach to take.

I am cur­rently work­ing on revised bench­marks for pro­cess­ing vs. threads vs. pp vs. other right now — I’ll be pub­lish­ing those as soon as I com­plete them to both here and the mail­ing list dis­cus­sion as a coun­ter­point to some of the open questions.

I’d like to see if any of you, oh inter­net peo­ple, have any­thing else you’d like to have answered for this or any­thing you’d like to add to the discussion.

Note, I am not try­ing to solve the “dis­trib­uted” prob­lem with the inclu­sion of this — the remote capa­bil­i­ties of the pro­cess­ing mod­ule are a side-benefit — not the pri­mary ben­e­fit to try­ing to get this in. I am tak­ing some of the dis­trib­uted stuff men­tally into account — but the goal is to scratch one spe­cific itch — not to solve every­ones prob­lem with a sin­gle addition.

Now all I have to get over is some bizarre errors with par­al­lel python ram­ming into ulimit, uh, lim­its. Luck­ily I have every­thing from a dual core to an eight core to hack on!

  • http://www.boddie.org.uk/paul Paul Bod­die

    Yes, take a look at http://wiki.python.org/moin/ParallelProcessing for a few pack­ages. My con­tri­bu­tion is the pprocess mod­ule which I actively use; that mod­ule and oth­ers pro­vide par­al­lel map func­tions which are arguably even more in tune with the aver­age programmer’s code than a thread­ing API, even though map has been frowned upon for quite some time by cer­tain core developers.

  • jnoller

    I tend to shy away from map as well — I never met a for-loop I didn’t like, but I will look at adding that to the mix as well. I’m quiet famil­iar with the Par­al­lel­Pro­cess­ing wiki page — I think I should just set it to my home­page and get it over with.

  • http://www.goldb.org Corey

    Nice! this would be a great addi­tion to the stdlib.

  • jnoller

    I’ve been think­ing about run­ning pylot with it :)

  • http://www.goldb.org Corey

    Nice! this would be a great addi­tion to the stdlib.

  • http://jessenoller.com jnoller

    I’ve been think­ing about run­ning pylot with it :)

What's this?

You are currently reading Getting Processing into the stdlib at jessenoller.com.

meta