[long] bzr with wsgi and gunicorn vs Pylons (paste)
Adrien Saladin
adrien at wizzi.net
Wed Oct 20 13:09:14 BST 2010
> Date: Tue, 19 Oct 2010 12:00:51 -0500
> From: John Arbash Meinel <john at arbash-meinel.com>
>
>> Is there a way to get more verbose output from the bzr wsgi application ?
>> I tried to set enable_logging=True but this does not seem to change anything.
>>
>> Also, is there a more verbose mode to the bzr client (or a plugin) to
>> get more informations about http traffic ?
>>
>> Thanks!
>>
>>
>
> Adding "-Dhpss" and "-Dhttp" to a bzr command could be useful. The
> client will then log (see 'bzr --version' for the log file) what
> requests are being made, and what HTTP requests/responses it receives.
>
Thank you for your help.
I now have a half-working solution. The problem was (and maybe still
is) about encoding.
With Pylons the wsgi.input environment variable is URL encoded. With a
call to "urllib.unquote_plus()" I have now bzr log and bzr branch
working correctly with bzr+http.
However bzr push still does not work. The bzr wsgi is configured with
write option enabled. Again this works like a charm with gunicorn so I
guess it is again a problem of encoding.
Do you know if "bzr push" messages can contain '+' signs or differs
from other bzr commands in some way ?
Thanks,
Adrien
More information about the bazaar
mailing list