Mon, 30 Jun 2008 10:36:45 +0200 hgweb: use a single-element tuple to return from protocol.unbundle()
Dirkjan Ochtman <dirkjan@ochtman.nl> [Mon, 30 Jun 2008 10:36:45 +0200] rev 6788
hgweb: use a single-element tuple to return from protocol.unbundle() Python 2.3/2.4 don't support yielding from inside try/finally blocks.
Sun, 29 Jun 2008 23:02:02 +0200 add an Accept header to the http client
Dirkjan Ochtman <dirkjan@ochtman.nl> [Sun, 29 Jun 2008 23:02:02 +0200] rev 6787
add an Accept header to the http client
Sun, 29 Jun 2008 22:47:57 +0200 tests: add a test for the hgweb graph
Dirkjan Ochtman <dirkjan@ochtman.nl> [Sun, 29 Jun 2008 22:47:57 +0200] rev 6786
tests: add a test for the hgweb graph
Sun, 29 Jun 2008 22:36:18 +0200 hgweb: return content iterator instead of using write() callable
Dirkjan Ochtman <dirkjan@ochtman.nl> [Sun, 29 Jun 2008 22:36:18 +0200] rev 6785
hgweb: return content iterator instead of using write() callable
Sun, 29 Jun 2008 15:23:09 +0200 hgweb: all protocol functions have become generators
Dirkjan Ochtman <dirkjan@ochtman.nl> [Sun, 29 Jun 2008 15:23:09 +0200] rev 6784
hgweb: all protocol functions have become generators Using the write() callable supplied by the start_response() call is frowned upon by the WSGI spec, returning an iterable over the content chunks is the recommended way. Be aware, though: returning many small chunks will slow down responses, because the server has to flush each chunk separately.
Sun, 29 Jun 2008 13:16:25 +0200 templater: make a template a string-only iterator
Dirkjan Ochtman <dirkjan@ochtman.nl> [Sun, 29 Jun 2008 13:16:25 +0200] rev 6783
templater: make a template a string-only iterator
Sun, 29 Jun 2008 14:20:01 +0200 streamclone yields chunks instead of accepting a file-like object
Dirkjan Ochtman <dirkjan@ochtman.nl> [Sun, 29 Jun 2008 14:20:01 +0200] rev 6782
streamclone yields chunks instead of accepting a file-like object
Sun, 29 Jun 2008 11:34:36 +0200 hgweb: protocol functions take repo instead of web
Dirkjan Ochtman <dirkjan@ochtman.nl> [Sun, 29 Jun 2008 11:34:36 +0200] rev 6781
hgweb: protocol functions take repo instead of web This makes it much easier for implementers of hgweb alternatives to simply call into protocol functions after setting up a repo and a request.
(0) -3000 -1000 -300 -100 -30 -10 -8 +8 +10 +30 +100 +300 +1000 +3000 +10000 +30000 tip