On Friday, July 13, 2018 at 4:59:06 PM UTC-7, Steven D'Aprano wrote:
...
> I think that Marko sometimes likes to stir the ants nest by looking down
> at the rest of us and painting himself as the Lone Voice Of Sanity in a
> community gone mad *wink*
...
You mean he thinks he's Ranting Rick?
Dal
On Dec 10, 2:23 pm, Carl Banks wrote:
> ...
> > A useful description of floating point issues can be found:
>
> [snip]
>
> I'm not reading it because I believe I grasp the situation just fine.
> ...
>
> Say I have two numbers, a and b. They are expected to be in the range
> (-1000,1000). As far
On Dec 7, 12:58 pm, Carl Banks wrote:
> On Dec 7, 10:53 am, dbd wrote:
> > ...
>
> You're talking about machine epsilon? I think everyone else here is
> talking about a number that is small relative to the expected smallest
> scale of the calculation.
>
> C
On Dec 7, 4:28 am, sturlamolden wrote:
> ...
>
> You don't understand this at all do you?
>
> If you have a sine wave with an amplitude less than the truncation
> error, it will always be approximately equal to zero.
>
> Numerical maths is about approximations, not symbolic equalities.
>
> > 1.0 +
t; > too much larger.
>
> > Okay, I'm confused now... I thought them being larger was entirely the
> > point.
>
> Yes. dbd got it wrong. If both a smaller than eps, the absolute
> difference is smaller than eps, so they are considered equal.
Small x,y failure case:
eps
On Dec 6, 1:12 am, Raymond Hettinger wrote:
> On Dec 5, 11:42 pm, Tim Roberts wrote:
>
> > Raymond Hettinger wrote:
>
> > > if not round(x - y, 6): ...
>
> > That's a dangerous suggestion. It only works if x and y happen to be
> > roughly in the range of integers.
.>
.> Right. Using abs(x-y)
On Jul 25, 10:20 am, Larry Bates <[EMAIL PROTECTED]> wrote:
> NicolasG wrote:
> > Dear fellows,
>
> > I'm trying to create a executable file using py2exe . Unfortunately
> > along with the python executable file it also creates some other files
> > that are needed in order to the executable be able
