At 17:30 24.08.2004 +0200, Jorgo Bakker wrote:
>Thanks for your comments.
>Updike, Clark wrote:
>>This behavior (and the workaround) is pretty clearly documented.
>I know, and I am not challenging the part of it that you included. Please
>note, that very document also said:
> "The possible signatures are sorted in a consistent order that
> should ensure the appropriate method is chosen first. *TBD:
> documentation this order!"*
>Now, it seems to me that for "x=2", "x" is a PyInteger, and the
>"appropriate method" should be for PyInteger and not Boolean! ... which
>brings me back to the bug issue.
>cheers - jorgo
it's (design) bug sitting there since forever, what you are trying I think
is somehow outside the scope of the original dispatch design. Dispatch
works pretty well for most practical purposes of calling preexisting Java
libraries, which has covered the fact, for a long time (but this is not the
first of the sparingly few related reports), that it has subtle issues.
The only workaround keeping all the signatures is to fix the method
PS: I'm not the author of the design dispatch as it stands, and revising it
is on the TODO list, also because of bool type introduction in Python.