Mon, 04 May 2009 21:18:33 +0900 inotify: Clarify the use of "watcher" name.
Nicolas Dumazet <nicdumz.commits@gmail.com> [Mon, 04 May 2009 21:18:33 +0900] rev 8335
inotify: Clarify the use of "watcher" name. Currently, Watcher is a class in inotify.linux.watcher, but it's also a class in inotify.server . To complicate things further more, the latter has a 'watcher' attribute, an instance of the former class. When it comes to the 'watcher' attribute of the Server class in inotify.server, one can get quite confused: is it a Watcher object from inotify.server, or from inotify.linux.watcher? Changes: * in inotify.linux.watcher : nothing * in inotify.server : ** Watcher class is renamed to RepoWatcher ** server.watcher is renamed to server.repowatcher
Mon, 04 May 2009 18:23:05 +0900 inotify: inotify.server.walk() filetype is never used, do not yield it
Nicolas Dumazet <nicdumz.commits@gmail.com> [Mon, 04 May 2009 18:23:05 +0900] rev 8334
inotify: inotify.server.walk() filetype is never used, do not yield it
Mon, 04 May 2009 20:26:27 +0200 allow http authentication information to be specified in the configuration
Sune Foldager <cryo@cyanite.org> [Mon, 04 May 2009 20:26:27 +0200] rev 8333
allow http authentication information to be specified in the configuration
Fri, 08 May 2009 18:30:44 +0200 patchbomb: quoted-printable encode overly long lines
Rocco Rutte <pdmef@gmx.net> [Fri, 08 May 2009 18:30:44 +0200] rev 8332
patchbomb: quoted-printable encode overly long lines RfC2822 mandates a line length limit of 998 byte + CRLF. Python mail tools break lines at 990 byte. To prevent that, we quoted-printable encode overly long lines.
Sat, 09 May 2009 01:15:24 +0200 patchbomb: fix quotes in help string
Martin Geisler <mg@lazybytes.net> [Sat, 09 May 2009 01:15:24 +0200] rev 8331
patchbomb: fix quotes in help string
Fri, 08 May 2009 15:52:26 -0700 Windows: improve performance via buffered I/O
Bryan O'Sullivan <bos@serpentine.com> [Fri, 08 May 2009 15:52:26 -0700] rev 8330
Windows: improve performance via buffered I/O The posixfile_nt code hits the win32 file API directly, which essentially amounts to performing a system call for every read and write. This is slow. We add a C extension that lets us use a Python file object instead, but preserve our desired POSIX-like semantics (the ability to rename or delete a file that is being accessed). If the C extension is not available (e.g. in a VPS environment without a compiler), we fall back to the posixfile_nt code.
Thu, 26 Mar 2009 13:14:35 -0700 win32: clarify comment regarding use of fdopen
Bryan O'Sullivan <bos@serpentine.com> [Thu, 26 Mar 2009 13:14:35 -0700] rev 8329
win32: clarify comment regarding use of fdopen
(0) -3000 -1000 -300 -100 -30 -10 -7 +7 +10 +30 +100 +300 +1000 +3000 +10000 +30000 tip