[sviet2k]

Hi,

I write an addon and I use command 'print' to debug my addon. The result of the print is saved in the kodi.log.
But currently I updated Kodi to Jarvis RC2 and there is no trace of my print in kodi.log
Does anyone know why ?

I am really appreciate for any help you can provide.

Thanks in advance,
sviet

[Martijn]

Enable debug

[sviet2k]

Hi Martijn,

Thanks for your quick prompt.
Sorry that I forgot to mention that I already turn on the debug in the System->Logging->Enable debug logging
But there is no trace of my print
Or may be is there other debug option ?

[wsnipex]

python stdout is mapped to debug level in kodi.log since v16 while it was info before. There were no other changes affecting this.

[Icerao]

Same question (and I m on windows), up to V16 to debug addon I just use print ' I m here' to debug them
Now to have that working, we need to enable debug logging that mean 200 debug garbage lines.

How we can make the 'print' command working like before (if it 's sill possible). The command xmbc.log() is working but less easy to use.

[wsnipex]

xbmc.log() is the correct way. Its not any "less easy" to use then print.

[Icerao]

Print is native fonction.
xbmc need to be imported.
Less syntax, less characters
Automatism for all devs (present in all language)

Lof of devs use this command to debug, I hope this change is realy usefull for other thing.