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] ABC issues
  • [Python-Dev] Slice as a copy... by design?
  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] ABC issues

[Python-Dev] ABC issues

Raymond Hettinger python at rcn.com
Tue May 27 20:50:34 CEST 2008

  • Previous message: [Python-Dev] ABC issues
  • Next message: [Python-Dev] Slice as a copy... by design?
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> If you want to use the 3.0 mixins in 2.6, perhaps an alternate set of
> APIs could be imported from the future? E.g. from future_collections
> import Mapping. IIRC a similar mechanism was proposed for some
> built-in functions, even though I see no traces of an implementation
> yet.

Any know what happened to the effort to put the 3.0 dict in future_builtins?

That would nicely sync-up the ABC with a concrete implementation
and bring 2.6 a little closer to 3.0.


Raymond

  • Previous message: [Python-Dev] ABC issues
  • Next message: [Python-Dev] Slice as a copy... by design?
  • 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.