Коренберг Марк
Коренберг Марк
http://bugs.python.org/issue16500 - Add an 'atfork' module
yes, I understand and have done exactly this workaround. But problem still exists.
The problem is in handling of numbers inside the binding.
one more example: ``` echo '"qwe \u05e9\u05dc\u05d5\u05dd 123 \u043f\u0440\u0438\u0432\u0435\u0442"' | jq -r ``` should give:  Note, `123` going (by bytes) after Hebrew should be rendered on the left side...
``` pylint 3.0.4 astroid 3.0.3 Python 3.12.2 (main, Feb 21 2024, 00:00:00) [GCC 13.2.1 20231205 (Red Hat 13.2.1-6)] ``` Still actual
Yes, you are right.Twsited just buffer that data in its head, and send it when possible. But we should wait when this write aactually complete in order to execute next...
I have discovered, that DBUS does not acknowledge that operation. Very sad. BUT. while experimenting I have found, that if I call `reactor.stop()` next after `conn.exportObject()`, I will not see...
Yes, thanks, that works! But still no _clean_ solution.
No, this does not work even with `yield None`. I have checked in debugger: it uses `inspect` module, and in this case, it unable to detect that I use `dbusCaller`...