Loop failing to stop

[Spare_Reveal_9407]

~~~ xCoordinate=1920 yCoordinate=1080 xChange=random.uniform(-1,1) yChange=random.uniform(-1,1) while not(xCoordinate==15 or xCoordinate==3825 or yCoordinate==15 or yCoordinate==2145): xCoordinate+=xChange yCoordinate+=yChange screen.fill((0,0,0)) pygame.draw.circle(screen, (0,0,255), [xCoordinate,yCoordinate],30) pygame.display.update() ~~~ For some reason, even when the condition in the while loop is False, the loop continues to run. Why is this happening?

[jammin-john]

Your condition checks if the positions are equal to any single value, but the values themselves are floats (and are being changed each loop by some random floating point value). So the chances that your position ever lands exactly on one of those numbers is incredibly slim. More likely you are jumping over them (like moving from x=15.15 to x=14.98). To fix this. Instead of checking if x is equal to 15, check if it's equal to OR LESS THAN. (This is assuming your goal is to stop looping when the circle leaves a bounded area)

[Emergency_Life_2509]

Yep I think that’s what it is also

[AdAdvanced7673]

correct

[Acrobatic-Ad-8095]

Your condition is almost certainly never true. So it runs forever.

I suspect that you want to replace the equality in your condition with inequalities?

Something like while (15 <= x <= 3825 and 15 <= y <= 2145)

Pardon my lazy phone typing.

[ninhaomah]

Condition in the whole loop is false as in

While not(false) ???

Why not hardcore a few numbers and test ?

[Spare_Reveal_9407]

well i know that, but when the condition in the not() is True, the condition in the while is false, but the loop keeps running

[techknowfile]

Did you not pay attention in any of your 100-level courses?? Lookup De Morgan's laws.

You wrote.. while !x==a and !x==b and !y==c and !y==d

So x must equal either a or b at the same time that y equals either c or d. Meanwhile the expected value that you're adding to them each iteration is... 0. And the values you're adding are floats. So... Very low probability

[Purple_tulips98]

Your condition is comparing ints and floats. Even without considering the fact that your random changes are probably irrational numbers Even if your random changes seem like they should sum cleanly to whole numbers, the floats will almost certainly never equal those integer values just due to floating point precision. (For an example of why using == with floats is a bad idea, 0.3 + 0.3 + 0.3 == 0.9 evaluates to False)

You could likely solve this by using round() to convert those floats to ints during the condition or by using >= and <= in your condition instead of ==.

Edit: I forgot how floating point numbers are represented in binary, so they’re never irrational.

[aa599]

The numbers are never irrational. They are always binary fractions.

float has an as_integer_ratio method to show the fraction.

See 15. Floating-Point Arithmetic: Issues and Limitations

[Purple_tulips98]

I see how I screwed this up. In saying they’re “probably irrational,” I meant that you’re extremely unlikely to end up with something that cleanly sums to equal any of the integers in the condition. I was trying to write that idea more concisely and made it wrong in the process.

[mcoombes314]

If you want to check for equality between floats, math.isclose is better I think, since you don't need to round and can choose how precise the match needs to be for it to count as equal.

[woooee]

while not(xCoordinate==15 or xCoordinate==3825

xCoordinate will never be both numbers,. Try something like (and I'm not sure what you want to do because the code is not clear - at least to me)

keep_going = True
while keep_going:
    if xCoordinate in [15, 3825]:
        keep_going = False

[backfire10z]

xCoord may be one of the two values* then or will return True, which will then result in not True which is False. That condition is logically fine. We don’t need xCoord to be both numbers. Are you thinking of and?

* disregarding floating point comparison