[egenix-users] Problems moving to mxTextTools 3.0

[Peter]

Thanks for your quick reply Marc-Andre,

>> Also could you clarify what is meant by "Removed support for
>> buffer-compatible input objects"? Does this mean we can't use Python's
>> StringIO handles?
> 
> Yes, we had to do this as a result of the restructuring of the
> underlying code which no longer works on a char* pointer, but
> instead uses the object type information to see whether it needs
> to compile a Unicode tag table or a string one.

Oh :(

I was afraid you might say that.

Do you have any suggested workarounds for using mxTextTools to parse 
data held in a string (rather than read from a handle to an opened file)?

Thanks

Peter