<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 13 Jun, 2012, at 2:58, ecir hana wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi,<div><br></div><div>I'm sorry I don't know what causes that in PyObjC but one option would be to try to do the same in cocoapy:</div><div><a href="http://code.google.com/p/cocoa-python/">http://code.google.com/p/cocoa-python/</a></div></blockquote><div><br></div>They don't seem to implement the part of PyObjC that the bug is in.</div><div><br></div><div>Anyway, I've switched the implementation for the "FAST_PATH" to one that's almost the same as that of the non-fast path, both now delegate to a (hidden) NSString instance. The only difference is that the FAST_PATH uses an NSString that uses the data storage of the PyUnicodeObject as the data storage for the string. That way there is no data duplication. I'm using a simular trick for Python 3.3: the implementation for __realObject__ won't copy data unless it really has to.</div><div><br></div><div>Ronald</div><div><br></div></body></html>