Your code is clobbering up variables.

Look at the variable names you are using on lines 2, 5, 9. Then try rubber-ducking your code. What actually happens when it breaks out of the for loop (not what you intended, I assume)

rubber ducking???

[url=https://en.wikipedia.org/wiki/Rubber_duck_debugging]https://en.wikipedia.org/wiki/Rubber_duck_debugging[/url]

iff is shorthand for "if and only if"
since having two divisors is sufficient and necessary for being prime, iff is the correct term here

edit: read here
[url]https://en.wikipedia.org/wiki/If_and_only_if[/url]

The full traceback is as follows:

[code]Traceback (most recent call last):
  File "./a", line 25, in 
    if prime == False:
NameError: name 'prime' is not defined [/code]

Traceback (most recent call last): 
  File "./a", line 25, in  
    if prime == False: 
NameError: name 'prime' is not defined 

thanks ^^

Your program is completely wrong, and thinks that 9 is a prime number.

What don't you like? PEG, or the PEG Judge? If you don't like PEG, then quit. If you don't like the Judge, I'm open to suggestions on how to improve it.

You can make your program faster by noticing that when you check whether a number is prime, you only need to test for factors up to the square root of the number.

I agree.

I just don't like the math part of PEG. I'm quite fond of programming.
And what does: .../ mean? (When you get answer wrong and you click details, or your output)

If you send me a screenshot I'll take a look.