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

  • [Python-Dev] Python 1.6 timing (fwd)
  • [Python-Dev] Python 1.6 timing (fwd)
  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] Python 1.6 timing (fwd)

[Python-Dev] Python 1.6 timing (fwd)

David Ascher [email protected]
Thu, 20 Jan 2000 16:01:45 -0800

  • Previous message: [Python-Dev] Python 1.6 timing (fwd)
  • Next message: [Python-Dev] Python 1.6 timing (fwd)
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Tim Peters

> But there's also been talk about moving (at least) the basic NumPy array
> type into the core.  This would be a Good Thing.

IMNSHO, moving the current NumPy array into the core would be a Bad Thing.
Moving a new similar object with cleaned up semantics and better
implementation in would be a Good Thing.  But it won't happen until 1.7 at
the earliest, as the semantics haven't even been agreed on, let alone the
code written.

--david




  • Previous message: [Python-Dev] Python 1.6 timing (fwd)
  • Next message: [Python-Dev] Python 1.6 timing (fwd)
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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.