RetroSearch Browse

Mon Nov 13 02:25:32 CET 2006 · https://mail.python.org/pipermail/python-dev/2006-November/069957.html

On 11/12/06, Anthony Baxter <anthony at interlink.com.au> wrote:
> On Sunday 12 November 2006 22:09, Fredrik Lundh wrote:
> > Martin v. Löwis wrote:
> > > Patch #1067760 deals with passing of float values to file.seek;
> > > the original version tries to fix the current implementation
> > > by converting floats to long long, rather than plain C long
> > > (thus supporting files larger than 2GiB).
>
> > > b) if not, should Python 2.6 just deprecate such usage,
> > >    or outright reject it?
> >
> > Python 2.5 silently accepts (and truncates) a float that's within range,
> > so a warning sounds like the right thing to do for 2.6.  note that read
>
> I agree that a warning seems best. If someone (for whatever reason) is
> flinging floats around where they actually meant to have ints, going straight
> to an error from silently truncating and accepting it seems a little bit
> harsh.

Right. There seem to be people who believe that 1e6 is an int.

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-November/069957.html below:

[Python-Dev] Passing floats to file.seek