This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Kuberan.Naganathan
Recipients Kuberan.Naganathan, neologix, pitrou, vstinner
Date 2011-07-13.15:24:29
SpamBayes Score 2.2324555e-06
Marked as misclassified No
Message-id <CAK=_o0iQEpvgRGb+M9fC7ouyQMBR8KdBdOZnr6JtN7XuR666ZQ@mail.gmail.com>
In-reply-to <1310558995.81.0.521451419494.issue12545@psf.upfronthosting.co.za>
Content
Im most familiar with solaris.  Atleast on solaris lseek interprets its
signed arg as the unsigned value with the same bit pattern.  I cannot be
certain that this is common across other operating systems.
On Jul 13, 2011 8:09 AM, "Antoine Pitrou" <report@bugs.python.org> wrote:
>
> Antoine Pitrou <pitrou@free.fr> added the comment:
>
>> In addition I would like the posix_lseek function to accept a value
>> larger than 2^63 as a seek offset
>
> How would it work? The C lseek() takes a signed (64-bit) offset as
argument, so we would have to call it multiple times anyway.
>
> ----------
> nosy: +neologix, pitrou
> versions: +Python 3.2, Python 3.3
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue12545>
> _______________________________________
Files
File name Uploaded
unnamed Kuberan.Naganathan, 2011-07-13.15:24:29
History
Date User Action Args
2011-07-13 15:24:30Kuberan.Naganathansetrecipients: + Kuberan.Naganathan, pitrou, vstinner, neologix
2011-07-13 15:24:29Kuberan.Naganathanlinkissue12545 messages
2011-07-13 15:24:29Kuberan.Naganathancreate