Message4825
I tried to produce a simple example that recreates the problem. That, of
course, didn't work.
I assume the issue is that lookup_where is not allowed to return an
object of type PyClass?
If lookup_where is allowed to return any type other than a PyType or one
of its descendants (and it's typed as PyObject so it could easily do
so), then I believe that the code is incorrect by inspection. The array
definition should be PyObject instead of PyType.
If, however, by convention lookup_where is only allowed to return
descendants of PyType (even though the type is PyObject) then the bug
lies elsewhere in something that's causing it to violate the convention.
If I can produce a simple example, I'll send it in. |
|
Date |
User |
Action |
Args |
2009-06-19 18:10:19 | rhudson@annapmicro.com | set | messageid: <1245435019.58.0.244599624724.issue1382@psf.upfronthosting.co.za> |
2009-06-19 18:10:19 | rhudson@annapmicro.com | set | recipients:
+ rhudson@annapmicro.com, pjenvey |
2009-06-19 18:10:19 | rhudson@annapmicro.com | link | issue1382 messages |
2009-06-19 18:10:19 | rhudson@annapmicro.com | create | |
|