| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
fixed typo in ihooks docstring
|
| | |
|
| |
|
|
|
|
| |
.readlines() methods. Inspired by a patch from Wolfgang Grafen,
though this version of the patch was completely rewritten from his
code.
|
| |
|
|
| |
called. catch the resulting AttributeError and exit cleanly.
|
| |
|
|
|
|
|
|
|
|
| |
*this* set of patches is Ka-Ping's final sweep:
The attached patches update the standard library so that all modules
have docstrings beginning with one-line summaries.
A new docstring was added to formatter. The docstring for os.py
was updated to mention nt, os2, ce in addition to posix, dos, mac.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
who writes:
Here is batch 2, as a big collection of CVS context diffs.
Along with moving comments into docstrings, i've added a
couple of missing docstrings and attempted to make sure more
module docstrings begin with a one-line summary.
I did not add docstrings to the methods in profile.py for
fear of upsetting any careful optimizations there, though
i did move class documentation into class docstrings.
The convention i'm using is to leave credits/version/copyright
type of stuff in # comments, and move the rest of the descriptive
stuff about module usage into module docstrings. Hope this is
okay.
|
| |
|
|
|
| |
the default arg for read() is -1, not None, and readlines() has an
optional argument (which for now is ignored).
|
| |
|
|
| |
Skip Montanaro's return-value patches.
|
| |
|
|
| |
object, if required.
|
| |
|
|
|
|
|
|
|
|
| |
1. Jack Jansen reports that on the Mac, the time may be negative, and
solves this by adding a write32u() function that writes an unsigned
long.
2. On 64-bit platforms the CRC comparison fails; I've fixed this by
casting both values to be compared to "unsigned long" i.e. modulo
0x100000000L.
|
| | |
|
| |
|
|
|
| |
support. (Based on comment on the documentation by Bernhard Reiter
<bernhard@csd.uwm.edu>).
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
allow using the 'a' flag as a mode for opening a GzipFile. gzip
files, surprisingly enough, can be concatenated and then decompressed;
the effect is to concatenate the two chunks of data.
If we support it on writing, it should also be supported on reading.
This *wasn't* trivial, and required rearranging the code in the
reading path, particularly the _read() method.
Raise IOError instead of RuntimeError in two cases, 'Not a gzipped file'
and 'Unknown compression method'
|
| | |
|
| |
|
|
| |
readlines() to behave like it should (return lines with "\n" appended).
|
| |
|
|
|
|
|
|
|
| |
problem was a couple of bugs in the readline implementation.
1. Include the '\n' in the string returned by readline
2. Bug calculating new buffer size in _unread
Also remove unncessary import of StringIO
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Here's my suggested replacement for gzip.py for 1.5.1. I've
re-implemeted methods readline and readlines, added an _unread, and
tweaked read and _read.
I tried a more complicated buffer scheme for unread (using a list of
strings and string.join), but it was more complicated and slower.
This version is a lot faster than the current version and is still
pretty simple.
|
| |
|
|
|
| |
Added _test() that behaves (a bit) like gzip.
Fix a comment (*sequential* access is okay -- *random* access it out!)
|
| |
|
|
| |
the need for the StringIO subclass.
|
|
|
This requires Andrew Kuchling's zlib extension module.
It still needs some doc strings.
|
