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] Issue 643841: Including a new-style proxy base class in 2.6/3.0

[Python-Dev] Issue 643841: Including a new-style proxy base class in 2.6/3.0

Michael Foord fuzzyman at voidspace.org.uk
Wed May 28 12:07:45 CEST 2008

  • Previous message: [Python-Dev] Issue 643841: Including a new-style proxy base class in 2.6/3.0
  • Next message: [Python-Dev] Issue 643841: Including a new-style proxy base class in 2.6/3.0
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Greg Ewing wrote:
> Nick Coghlan wrote:
>
>>     else:
>>         # Returned a different object, make a new proxy
>>         result = type(self)(result)
>
> You might want to check that the result has the
> same type as the proxied object before doing that.
>
Yep - and I really think it would need to do this. To have a proxy where:

proxy_instance += 1

unwraps the proxy is really no good! (At least not for my use cases...)

Michael Foord

-- 
http://www.ironpythoninaction.com/
http://www.theotherdelia.co.uk/
http://www.voidspace.org.uk/
http://www.ironpython.info/
http://www.resolverhacks.net/


  • Previous message: [Python-Dev] Issue 643841: Including a new-style proxy base class in 2.6/3.0
  • Next message: [Python-Dev] Issue 643841: Including a new-style proxy base class in 2.6/3.0
  • 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.