Example code: # -*- coding: utf-8 -*- def test(): """ Описание description """ None test() The non-ASCII string in the docstring is not displayed properly in the tool tip. Reproducible: Always
*** Bug 317882 has been marked as a duplicate of this bug. ***
Created attachment 82172 [details] Incorrect disply docstring with non-ascii characters
kdev-python version 1.5.1
Created attachment 82399 [details] patch for partial correct problem I resolve describle problem. See docstring-coding.diff But problem reproduce for unicode docstrings and non utf-8 source encoding.
Git commit 5efbfef3ca5fb6a10fc43338c708599485c4e5c9 by Sven Brauch. Committed on 19/09/2013 at 08:02. Pushed by brauch into branch 'master'. Fix character encoding in comments. Patch effectively by Alexandr Zamaraev <tonal.promsoft@gmail.com> with some corrections. M +5 -5 parser/astbuilder.cpp M +5 -5 parser/conversionGenerator.py M +13 -13 parser/generated.h http://commits.kde.org/kdev-python/5efbfef3ca5fb6a10fc43338c708599485c4e5c9
Great work, thanks for taking this into your own hands -- and sorry for not doing it myself ;) Your provided patch was indeed the correct solution, I just had to rework it a bit. The problems with non-UTF8 source encodings can also be fixed, since we can force the parser through a flag to always read the text we give it as utf-8, and in kate we'll always have the same encoding anyways. Thanks again! Cheers, Sven
Сan we hope for bekport to branch 1.5?
Git commit eec4e51d5ee6cb738386ed824bb19c1c133b1782 by Sven Brauch. Committed on 19/09/2013 at 08:02. Pushed by brauch into branch '1.5'. Fix character encoding in comments. Patch effectively by Alexandr Zamaraev <tonal.promsoft@gmail.com> with some corrections. M +5 -5 parser/astbuilder.cpp M +5 -5 parser/conversionGenerator.py M +13 -13 parser/generated.h http://commits.kde.org/kdev-python/eec4e51d5ee6cb738386ed824bb19c1c133b1782
Yeah can do, but I can't promise there'll be another release of 1.5; it's not even terribly likely at this point, since it's not too bad.