[Python-Dev] release for 2.1.2, plus 2.2.1...

Martin v. Loewis martin@v.loewis.de
Fri, 4 Jan 2002 20:49:24 +0100


> I'm subscribed to the list, but I'm still not quite sure if I'm supposed to
> be posting here... I suppose I should go read the charter.  Please flame me
> if this list is for the "in crowd" only. ;-)

This list is for development *of* Python. Anybody is free to post
questions and comments on that topic, like you just did; I don't like
it when people post questions of the "how do I ... in Python" kind
that you typically see on python-list - this is not a list to get
better help :-)

> I tried to get the 21-maintbranch LFS working using the directions that are
> provided in the current docs
> (http://www.python.org/doc/current/lib/posix-large-files.html), but it fails
> to compile for me as a result.  Someone has suggested that it's not the
> instructions that are broken, but the code.  Can this be confirmed?

Well, you did not describe exactly how it fails to compile for
you. Assuming you got an error that something is not an integral type,
then that is clearly an error in the code. You might want to
investigate the error message you get more closely; please confirm
that it refers to the return value of fgetpos.

If you need further confimation, I recommend that you invoke the gcc
line that fails adding --save-temps, and inspect the resulting
fileobject.i. You will likely find that fpos_t is a structure, and
that Python attempts to return it in a place where an integer is
needed (or vice versa).

> Because ZC is forced to stick with Python 2.1.X (as opposed to 2.2.X) for
> the current crop of Zope releases, and because we often need large file
> support under Zope, it's pretty important for us to get a 2.1.X release
> under which LFS works.  A workaround is fine as well.

Please try the patch I posted, and report whether test_largefile
passes or fails (or, if it fails to compile, what the exact error
messages are).

Regards,
Martin