[QScintilla] Another QScintilla Unicode issue
bazwal at ftml.net
Sun Aug 15 14:57:44 BST 2010
On 14/08/10 22:49, Phil Thompson wrote:
> On Sat, 14 Aug 2010 22:41:07 +0100, Baz Walter<bazwal at ftml.net> wrote:
>> On 14/08/10 16:29, Phil Thompson wrote:
>>> I may make it more restrictive (ie. more correct, but maybe at the cost
>>> breaking code) by requiring bytes objects (for Python3) and str objects
>>> (for Python2), and no longer allowing str objects (for Python3) and
>>> objects (for Python2).
>> fwiw, this sounds fine to me - i have always done things that way as it
>> seems the most pythonic (EIBTI and all that).
>> just to be clear, though: if you did this, it would still be possible to
>> pass a bytearray to the scintilla apis that /retrieve/ text, right?
> Can you give me a specific example?
not sure how specific you meant, but most of my usage involves code like:
result = bytearray(end - start)
self.SendScintilla(MESSAGE, start, end, result)
where MESSAGE can be any of SCI_GETTEXTRANGE, SCI_GETSELTEXT,
the code would then go on to use the bytearray directly and/or decode to
a unicode object.
from a python point of view, i suppose it might be nicer if those apis
returned a tuple of (length, bytes) rather than modifying the argument.
More information about the QScintilla