2 GB files

David M. Cooke cookedm+news at physics.mcmaster.ca
Mon Aug 23 03:13:11 CEST 2004


At some point, "David Pokorny" <davebrok at soda.csua.berkeley.edu> wrote:

> "Elbert Lev" <elbertlev at hotmail.com> wrote in message
> news:9418be08.0408221427.182a4d30 at posting.google.com...
>> From postings to this group and other resources I understood that the
>> only way to make Python programs to work correctly with files lager
>> then 2 GB is building Python interpreter with some "magic spell"
>> defines. For me this is ABSOLUTELY unacceptable (Not the building, but
>
> Elbert: you might get a positive response if you rephrased your post.
>
> "Our corporation needs functionality ___. We would be happy to pay a
> contract consultant $n000 to come up with a solution that will work with a
> future trajectory of Python releases."
>
> Or you could pray to the OSS gods.

Or do better research, as it already has it.

My python (from Debian) has large file support, for instance. Python's
configure script will use if it can find it.

The OP doesn't mention what he's using that doesn't have large files
(OS, platform, python version...)

-- 
|>|\/|<
/--------------------------------------------------------------------------\
|David M. Cooke
|cookedm(at)physics(dot)mcmaster(dot)ca



More information about the Python-list mailing list