On 4/9/06, Frank Cohen <fcohen@...> wrote:
> Whatever happened to the String CharSequence issue in Jython 2.1? I
> remember a while back that calls to a Java class that required a
> String parameter cause Jython to generate an exception:
The current 2.2 code uses Class.isAssignableFrom() instead of
explicitly matching against a list of classes as in 2.1. A quick test
with java Pattern.matcher() now succeeds, so it seems one of the
trusty jython developers has already fixed that.