- 06 Agu, 2002 23 kayıt (commit)
-
-
Fred Drake yazdı
-
Guido van Rossum yazdı
Fix forthcoming.
-
Fred Drake yazdı
Closes SF bug #586937.
-
Barry Warsaw yazdı
Py_UNICODE.
-
Barry Warsaw yazdı
width of Py_UNICODE. Good catch, MAL.
-
Skip Montanaro yazdı
same idea as getting rid of GETCONST & GETNAME (see patch #506436)
-
Guido van Rossum yazdı
-
Guido van Rossum yazdı
version to 1.1.4 (because of the 1.1.3 security problem). Also replace a funny use of line.find() with line.startswith().
-
Guido van Rossum yazdı
machine -- that feels just right.
-
Guido van Rossum yazdı
is no longer unused in type objects.
-
Guido van Rossum yazdı
-
Guido van Rossum yazdı
-
Barry Warsaw yazdı
-
Guido van Rossum yazdı
module). (One thing remains to be done: the gzip class has an xreadline method; this ought to be replaced by an iterator as well.)
-
Barry Warsaw yazdı
string of longer than 1 character.
-
Guido van Rossum yazdı
are obsolete.
-
Steve Holden yazdı
-
Guido van Rossum yazdı
ValueError when called for a closed file.
-
Guido van Rossum yazdı
For a file f, iter(f) now returns f (unless f is closed), and f.next() is similar to f.readline() when EOF is not reached; however, f.next() uses a readahead buffer that messes up the file position, so mixing f.next() and f.readline() (or other methods) doesn't work right. Calling f.seek() drops the readahead buffer, but other operations don't. The real purpose of this change is to reduce the confusion between objects and their iterators. By making a file its own iterator, it's made clearer that using the iterator modifies the file object's state (in particular the current position). A nice side effect is that this speeds up "for line in f:" by not having to use the xreadlines module. The f.xreadlines() method is still supported for backwards compatibility, though it is the same as iter(f) now. (I made some cosmetic changes to Oren's code, and added a test for "file closed" to file_iternext() and file_iter().)
-
Jack Jansen yazdı
if we are running in an OSX framework enabled build directory, test that the framework infrastructure exists. This catches the very common error of doing "make install" in stead of "make frameworkinstall".
-
Jack Jansen yazdı
at compile time: use PBGetCatInfoSync() to get FInfo data in stead of GetFInfo. The latter doesn't work for folders. The former does, at least on OSX, and insofar the info makes sense for a folder.
-
Jack Jansen yazdı
-
Andrew M. Kuchling yazdı
Document heapq module Add PEP263 section (not sure I really understand the PEP's effect on 8-bit strings, though -- will have to experiment with it)
-
- 05 Agu, 2002 17 kayıt (commit)
-
-
Neal Norwitz yazdı
-
Fred Drake yazdı
-
Jack Jansen yazdı
check whether it contains a .nib, and do the Cocoa song and dance if it does.
-
Jack Jansen yazdı
exists. Partial fix for #585923.
-
Jack Jansen yazdı
-
Jack Jansen yazdı
Handle the two modules with non-standard scanner module names.
-
Jack Jansen yazdı
-
Jeremy Hylton yazdı
-
Jeremy Hylton yazdı
xxxPyCObject_Import() seems to be a copy of PyCObject_Import().
-
Fred Drake yazdı
setup.py (indirectly) script to build the standard dynamically loaded modules, the errno module is being made static so it will always be available. Closes SF bug #591205 (needed on trunk only).
-
Guido van Rossum yazdı
-
Guido van Rossum yazdı
1) Do not attempt to exec a file which does not exist just to find out what error the operating system returns. This is an exploitable race on all platforms that support symbolic links. 2) Immediately re-raise the exception if we get an error other than errno.ENOENT or errno.ENOTDIR. This may need to be adapted for other platforms. (As a security issue, this should be considered for 2.1 and 2.2 as well as 2.3.)
-
Jack Jansen yazdı
-
Jack Jansen yazdı
-
Jack Jansen yazdı
to search on the command line in that case.
-
Jack Jansen yazdı
possibly being missing.
-
Fred Drake yazdı
-