Thanks Geoff!
I downloaded your fix and by putting in the print statement verified I was
getting multiple copies of UnboundMethodError before the fix and only one
after the fix.
If I understand the problem correctly, the className.methodName(self,...)
form of call does a global lookup and th
I just checked in a fix to Webware CVS. Give it a try.
- Geoff
On Sun, 2002-07-14 at 12:36, Geoff Talvola wrote:
> This isn't a Python problem -- it's a bug in Webware.
>
> If you put a print statement at the end of UnboundMethodError.py you'll
> find that the module actually gets imported mul
This isn't a Python problem -- it's a bug in Webware.
If you put a print statement at the end of UnboundMethodError.py you'll
find that the module actually gets imported multiple times. This
somehow causes a mismatch between the instances and the classes that
triggers the error you're noticing.
I got lucky yesterday and stumbled across a solution which has been right in
front of me on the failing line. My problem seems to be rooted in Python. I
wrote the following with the intention of posting to the Python bug list.
Does this sound reasonable?
TypeError: unbound Method
I some
