Why Is This Not a Syntax Error

Why Is There No Syntax Error In This Code?

SyntaxError:

Syntax errors are produced by Python when it is translating the source code into byte code. They usually indicate that there is something wrong with the syntax of the program.

Simply dog.bark is going to reference the function. It is completely valid. Sometimes, you must have got some weird message telling some function name at memory location. That is because it printed the function, which was referenced and not called.

Python will simply interpret that as usual. There is nothing wrong with the syntax

Why is using not() operator sometimes a SyntaxError?

The problem is the use of == where you need =. This normally wouldn't cause a syntax error, but in your case, you have:

a == not(b)

which is the same as:

a == not b

This groups as:

(a == not) b

and that causes the syntax error.

An assignment operator, on the other hand, has lower precedence, so:

a = not b

groups as:

a = (not b)

which is fine.

Python: Syntax Error that is not a Syntax Error?

You almost certainly ended line 1121 incorrectly somehow, and the Python interpreter expected the incomplete expression to be continued onto line 1122. When it could not parse 1122 as a continuation of 1121, that is what caused the syntax error, rather than anything particularly wrong with line 1122 itself.

Also, it is not true that "f.write is only good for xyz number of lines"; to demonstrate I wrote the following test-program generator:

import random
import string

GENFILE = "testwrite.py"
HEADER  = "with open('testout.txt', 'a') as f:\n"
BODY    = "    f.write(\"{}\")\n"
BODY_N  = 100000

def randstr(n = 1, ch=string.lowercase):
    return ''.join(random.choice(ch) for i in xrange(n))

def main():
    with open(GENFILE, 'w') as outf:
        outf.write(HEADER)
        for i in xrange(BODY_N):
            outf.write(BODY.format(randstr(10)))

if __name__=="__main__":
    main()

which created a program that looks like

with open('testout.txt', 'a') as f:
    f.write("ugakajlxkv")
    f.write("tskhodwgwr")
    f.write("vrqcrnxhcz")
    f.write("yijyqfyjug")
    f.write("gbsthkkkdc")
    f.write("vmupgtotoe")
    # ... 99,994 more lines

which runs quite happily.

Why is this code getting invalid syntax error?

You're missing a closing bracket:

def compare(A: object, B: object) -> object:
    if(A>B):
        return A
    elif(A<B):
        return B
    else:
        return A

if __name__ == "__main__":
    A = int(input())
    scorelist = []

    for i in range(0,A):
        tmp = int(input())
        scorelist.append(tmp)

    sum =+ int(scorelist[0])
    k = 1
    for j in A-2:
        D = compare(scorelist[k],scorelist[k+1])
        k = scorelist.index(D)
        sum =+ D

    print (sum)
    print(scorelist)

Why is this not a syntax error?

Line endings are optional, so in this case, the return is causing the parser to interpret it as the following:

(false; true)

which evaluates to just:

(true)

If these were method calls then both would be evaluated, but only the last would be emitted. For example:

x = (p "hello"
p "world"
2)

This will output "hello" and "world" and x will equal 2

Why isn't this a syntax error in python?

Whitespace between tokens

Except at the beginning of a logical line or in string literals, the whitespace characters space, tab and formfeed can be used interchangeably to separate tokens. Whitespace is needed between two tokens only if their concatenation could otherwise be interpreted as a different token (e.g., ab is one token, but a b is two tokens).

So in this case, 1if is not a valid token, so the whitespace is optional. The 1 is interpreted as an integer literal of which the if is not a part. So if is interpreted separately and recognized as a keyword.

In xif however, an identifier is recognized, so Python is not able to see that you wanted to do x if there.

Syntax error in python for some reason I do not know

int is not closed with ‘)’. Please close it to wipe this error.

Why am I getting a syntax error when using the = operator?

It is a design mistake.

I have turned to use >= as the operator for bind() and deprecated >>=. A new release of parsec.py has been upload to pypi.

---

Related Topics