Re: [Python-Dev] floatobject.c 2.136

2005-07-04 Thread Michael Hudson
On 4 Jul 2005, at 18:59, Raymond Hettinger wrote: > P.S. I still don't follow the whole yours/mine comment from Michael. > The offending code line was part of 2.136 which CVS says was checked-in > by him on 5/27/2005 and then fixed by him on 6/30/2005. Well, my confusion started and ended with t

Re: [Python-Dev] floatobject.c 2.136

2005-07-04 Thread Raymond Hettinger
> Alas, a typical exchange. The checkins are mailed from the committer's > Sf email address, but the mailing list has been set up to redirect all > replies to python-dev -- if you don't catch this before sending, you > may be embarrassed in public or confuse the addressee. > > Is this behavior of

Re: [Python-Dev] floatobject.c 2.136

2005-07-04 Thread Guido van Rossum
[Raymond Hettinger] > > I'm getting a compiler warning from your checkin: [Michael Hudson] > "your"? Mine? Alas, a typical exchange. The checkins are mailed from the committer's Sf email address, but the mailing list has been set up to redirect all replies to python-dev -- if you don't catch thi

Re: [Python-Dev] floatobject.c 2.136

2005-06-29 Thread Michael Hudson
"Raymond Hettinger" <[EMAIL PROTECTED]> writes: > I'm getting a compiler warning from your checkin: "your"? Mine? > C:\py25\Objects\floatobject.c(1430) : warning C4244: 'initializing' : > conversion from 'double ' to 'float ', possible loss of data That's this line: float y = x;