GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] Addition of "pyprocessing" module to standard lib.

[Python-Dev] Addition of "pyprocessing" module to standard lib.

Nick Coghlan ncoghlan at gmail.com
Thu May 15 12:10:01 CEST 2008

  • Previous message: [Python-Dev] Addition of "pyprocessing" module to standard lib.
  • Next message: [Python-Dev] Addition of "pyprocessing" module to standard lib.
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Gregory P. Smith wrote:
> -1 on "multicore" - multiprocess or multiprocessing are a fine names.
> cores are irrelevant.  systems have multiple cpus real or virtual
> regardless of how many dies, sockets and cores there are.
> 
> +0.5 on inclusion.  that means i am happy if it does but don't think
> it needs to make it into 2.6/3.0.  leave inclusion for 2.7/3.1.  its
> easy for people to install from an external source for now if they
> want it.

This is a nice summary of my opinion as well.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
---------------------------------------------------------------
             http://www.boredomandlaziness.org

  • Previous message: [Python-Dev] Addition of "pyprocessing" module to standard lib.
  • Next message: [Python-Dev] Addition of "pyprocessing" module to standard lib.
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Python-Dev mailing list
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.