Bug on Python2.3.4 [FreeBSD]?

[Donn Cave]

Quoth "Terry Reedy" <tjreedy at udel.edu>:
| "Donn Cave" <donn at u.washington.edu> wrote in message 
| news:donn-BC56BC.16011812082005 at gnus01.u.washington.edu...
| > I don't think Python pretends to have any intentions here,
| > it has to take what it gets from the C library fopen(3)
| > function.  BSD man pages generally say a+ positions the
| > stream at end of file (period.)  They claim conformance
| > with the ISO C90 standard.  I couldn't dig up a (free) copy
| > of that document, so don't know what it says on this matter.
|
| STandard C, by Plauger & Brodie says that 'a' plus whatever else means all 
| writes start at the current end-of-file.

Of course, but the question was, where do reads start?  I would
guess the GNU C library "innovated" on this point.  But in the
end it doesn't really matter unless Python is going to try to
square that all up and make open() consistent across platforms.

	Donn Cave, donn at drizzle.com