[PEAK] Strange dispatch problem after cvs up
Phillip J. Eby
pje at telecommunity.com
Sun Apr 24 03:33:39 EDT 2005
At 09:02 AM 4/21/05 -0400, Jay Parlar wrote:
>Fantastic, importing dispatch.strategy first worked for me. Not a good
>long term solution, but at least I can get back to it.
Okay, I've checked in a fix. It turns out it wasn't an import circularity,
but rather it's the fact that you can't nest "assignment advisors" -- my
evil trace-hook hack to simulate decorators in Python <2.4. What was
happening is that if the first time dispatch.strategy was imported was from
a decorator (like 'someGF.when()'), then an important 'dispatch.as()' call
would silently fail, mucking up the "make_index" method's setup as a
classmethod.
Anyway, it's fixed now, but we should probably make a move to Python 2.4 in
the near future in order to get away from this problem.
More information about the PEAK
mailing list