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] PEP 231, __findattr__()
  • [Python-Dev] PEP 231, __findattr__()
  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] PEP 231, __findattr__()

[Python-Dev] PEP 231, __findattr__()

Moshe Zadka [email protected]
Tue, 05 Dec 2000 05:31:18 +0200

  • Previous message: [Python-Dev] PEP 231, __findattr__()
  • Next message: [Python-Dev] PEP 231, __findattr__()
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> I'm still catching up on several hundred emails over the weekend.  I
> had a sneaking suspicion that infindattr wasn't thread-safe, so I'm
> convinced this is a bug in the implementation.  One approach might be
> to store the info in the thread state object

I don't think this is a good idea -- continuations and coroutines might
mess it up. Maybe the right thing is to mess with the *compilation* of
__findattr__ so that it would call __setattr__ and __getattr__ with
special flags that stop them from calling __findattr__? This is 
ugly, but I can't think of a better way.
-- 
Moshe Zadka <[email protected]>
This is a signature anti-virus. 
Please stop the spread of signature viruses!



  • Previous message: [Python-Dev] PEP 231, __findattr__()
  • Next message: [Python-Dev] PEP 231, __findattr__()
  • 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.