Alexander Belchenko wrote:
DeeJay пишет:
bzrw writes log to C:\Program Files\Bazaar\bzrw.exe.log
Yes, I know, this happens when some code tries to write to
stdout/stderr.
Can you tell me when this happens?
I've got another instance -
Using BE, Open a Location with an old repository. The 'deprecated'
warning goes to <pathto_bzr>bzrw.exe.log, which then contains -
Format <RepositoryFormatKnit1> for file:///F:/bzrtempco/broken/.bzr/
is deprecated - please use 'bzr upgrade' to get better performance
Okay.
So... We need to improve bzrw.py script by override trace.py logging
behavior and redirect note/info messages to MemoryHandler instead of
StreamHandler (stderr) and hope that everything in bzrlib uses trace.*
methods instead of direct writing to stderr.
Ian, do you think we need to add special status/debug console in Bazaar
Explorer to (optionally) show these messages?
It's fairly easy detect that we are working with bzrw (by check
sys.frozen == 'windows_exe'), so maybe Bazaar Explorer should change
logging settings of trace.py on start? Ditto for QBzr dialogs?
I would just mention that it would make a lot more sense *to me* to have
a separate "bzr-explorer.exe" main script. And this would bootstrap into
'bzr explorer', only setting up everything as you would expect a gui to
behave. So it would have its own 'main()' function, rather than using
bzr's main, just to have stuff like ui_factory get overridden, and set
up trace to log as expected, etc.
It also means that there is a simple icon to double-click, which can
have, etc, etc.
Then again, maybe you need bzrw because you want to run a subprocess
without a console window. Which is fine, I just figured I would mention
a potentially better entry point than "bzrw explorer".
John
=:->
