[issue12545] Incorrect handling of return codes in the posix_lseek function in posixmodule.c
Kuberan Naganathan
report at bugs.python.org
Wed Jul 13 17:24:30 CEST 2011
Kuberan Naganathan <kubiyak at gmail.com> added the comment:
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 at bugs.python.org> wrote:
>
> Antoine Pitrou <pitrou at 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 at bugs.python.org>
> <http://bugs.python.org/issue12545>
> _______________________________________
----------
Added file: http://bugs.python.org/file22641/unnamed
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue12545>
_______________________________________
-------------- next part --------------
<p>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. </p>
<div class="gmail_quote">On Jul 13, 2011 8:09 AM, "Antoine Pitrou" <<a href="mailto:report at bugs.python.org">report at bugs.python.org</a>> wrote:<br type="attribution">> <br>> Antoine Pitrou <<a href="mailto:pitrou at free.fr">pitrou at free.fr</a>> added the comment:<br>
> <br>>> In addition I would like the posix_lseek function to accept a value<br>>> larger than 2^63 as a seek offset<br>> <br>> 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.<br>
> <br>> ----------<br>> nosy: +neologix, pitrou<br>> versions: +Python 3.2, Python 3.3<br>> <br>> _______________________________________<br>> Python tracker <<a href="mailto:report at bugs.python.org">report at bugs.python.org</a>><br>
> <<a href="http://bugs.python.org/issue12545">http://bugs.python.org/issue12545</a>><br>> _______________________________________<br></div>
More information about the Python-bugs-list
mailing list