Unexpected token python ошибка

1. Error: bash: syntax error near unexpected token '(' in Python
2. Fix Error: bash: syntax error near unexpected token '(' in Python

Every time a Python code runs through a shell terminal such as Bash, it must point to an interpreter. If Bash cannot find a suitable way to run the file, then it will give out errors.

This guide will discuss Error: Bash: syntax error near unexpected token '('.

Error: bash: syntax error near unexpected token '(' in Python

Python needs to be installed on your computer for the interpreter to find and run the Python files. The interpreter works differently in different operating systems.

In Windows, when we install Python, a program called IDLE is installed on the computer, which comes with the interpreter. It runs Python codes.

In Linux, we can access Python using the shell terminal by typing the command python. It opens the Python environment where the code can be written and run.

If the code has trouble finding the Python interpreter, it will run on whichever shell it runs. If the user runs the code from the Bash terminal, then the shell will give an error that will resemble this:

#Python 3.x
Error: bash: syntax error near unexpected token '('

Bash is a Unix command and is the default shell for most Linux distributions. It cannot understand Python code, so it gives out this error.

It might not give an error on the first line of the code and will give the error later because it might interpret some of the code as a shell command.

Fix Error: bash: syntax error near unexpected token '(' in Python

There are multiple ways to fix this error in Python. The fixes vary between Linux and Windows because these operating systems work differently.

Solutions for Linux

The path to the interpreter should be added to the code file so that the computer knows the interpreter has to run this file and not the shell terminal. We should add the following line at the top of the code file:

#Python 3.x
#!/usr/bin/env python

It runs the file from the Python interpreter, not the Bash shell. We have to note that this is not a Python comment.

Instead, this shell command starts the Python environment in the shell before running the code. The user can also run the code file on the shell by giving the python command before the file name, like python filename.py.

It also does the same and runs the file from the Python interpreter. If we have both Python 2 and 3 installed, we need to write python3 if we want to run the code using Python 3. And just python if we want to run the code using Python 2.

Example Code:

#Python 3.x
#!/usr/bin/env python
print("Hello World")

Output:

Solution for Windows

In Windows, the user can also use the python keyword in the terminal to run the code file, but before doing so, the path to the Python interpreter needs to add to the PATH variable of Windows. The steps to do that are:

1. Search for env in the Windows search bar and open the Edit the system environment variables option.
2. Now open the Environment Variables.
3. Now, choose the PATH variable and click on Edit.
4. Paste the interpreter’s path in an empty field in this window.
5. The path to the interpreter is now added to the user’s Windows, and we can use the python command to run the code files from the shell.

Now we need to write the following in a terminal to run the code:

#Python 3.x
python filename.py

While running the simple Python program below, I’m getting the following error:

./url_test.py: line 2: syntax error near unexpected token `('                  
./url_test.py: line 2: `response = urllib2.urlopen('http://python.org/')'

import urllib2      
response = urllib2.urlopen('http://python.org/')  
print "Response:", response

# Get the URL. This gets the real URL. 
print "The URL is: ", response.geturl()

# Getting the code
print "This gets the code: ", response.code

# Get the Headers. 
# This returns a dictionary-like object that describes the page fetched, 
# particularly the headers sent by the server
print "The Headers are: ", response.info()

# Get the date part of the header
print "The Date is: ", response.info()['date']

# Get the server part of the header
print "The Server is: ", response.info()['server']

# Get all data
html = response.read()
print "Get all data: ", html

# Get only the length
print "Get the length :", len(html)

# Showing that the file object is iterable
for line in response:
 print line.rstrip()

# Note that the rstrip strips the trailing newlines and carriage returns before
# printing the output.

Thanks for the responses. I thought about it a bit and decided to look for a python-native way to do it. There was enough information at the python cryptography cheatsheet website and others that I was able to put together the python code to generate the CSR.

requires pyOpenSSL


from cryptography.hazmat.backends import default_backend
from cryptography.hazmat.primitives import serialization
from cryptography.hazmat.primitives.asymmetric import rsa
key = rsa.generate_private_key(
public_exponent=65537,
key_size=2048,
backend=default_backend())

with open('mycert.key', 'wb') as f:
     f.write(key.private_bytes(
     encoding=serialization.Encoding.PEM,
     format=serialization.PrivateFormat.TraditionalOpenSSL,
     encryption_algorithm=serialization.NoEncryption()))

from OpenSSL import crypto

# load private key
ftype = crypto.FILETYPE_PEM
with open('mycert.key', 'rb') as f: key = f.read()
key = crypto.load_privatekey(ftype, key)
req    = crypto.X509Req()

alt_name  = [ b"DNS:mynode",
              b"DNS:myF5",
              b"email:administratore@email.com" ]
key_usage = [ b"Digital Signature",
              b"Key Encipherment" ]
key_usage = [ b"digitalSignature",
              b"keyEncipherment" ]
ext_key_usage = [ b"serverAuth",
                  b"clientAuth" ]

# country (countryName, C)
# state or province name (stateOrProvinceName, ST)
# locality (locality, L)
# organization (organizationName, O)
# organizational unit (organizationalUnitName, OU)
# common name (commonName, CN)

req.get_subject().C  = "US"
req.get_subject().ST = "Florida"
req.get_subject().L  = "St Petersburg"
req.get_subject().O  = "myCompany"
req.get_subject().OU = "MyOU"
req.get_subject().CN = "mynode"
req.add_extensions([
    crypto.X509Extension( b"basicConstraints",
                          False,
                          b"CA:FALSE"),
    crypto.X509Extension( b"keyUsage",
                          False,
                          b",".join(key_usage)),
    crypto.X509Extension( b"subjectAltName",
                          False,
                          b",".join(alt_name))
])

req.set_pubkey(key)
req.sign(key, "sha256")

csr = crypto.dump_certificate_request(ftype, req)
with open("mycert.csr", 'wb') as f: f.write(csr)

I’m getting the issue as well. I believe I’m using the new language server, but don’t have a way to check. I’m also getting like 10 other parsing errors that are also false alarms, but I can open a new issue for those if desired.

The code for the above problems is hangouts_parser.py from er0sin/hangouts_to_sms

For people who use text search, I’ll copy the issues below:

Below are the json error reports:

The Error Reports

{
	"resource": "/c:/Users/USERNAME/odrive/Google Drive/Random/Hangouts2Messages-SMS/hangouts_to_sms_er0sin/hangouts_parser.py",
	"owner": "_generated_diagnostic_collection_name_#0",
	"code": "E16",
	"severity": 8,
	"message": "invalid syntax",
	"source": "Python (parser)",
	"startLineNumber": 10,
	"startColumn": 61,
	"endLineNumber": 10,
	"endColumn": 64
}
{
	"resource": "/c:/Users/USERNAME/odrive/Google Drive/Random/Hangouts2Messages-SMS/hangouts_to_sms_er0sin/hangouts_parser.py",
	"owner": "_generated_diagnostic_collection_name_#0",
	"code": "E16",
	"severity": 8,
	"message": "unexpected token 'open'",
	"source": "Python (parser)",
	"startLineNumber": 25,
	"startColumn": 14,
	"endLineNumber": 25,
	"endColumn": 18
}
{
	"resource": "/c:/Users/USERNAME/odrive/Google Drive/Random/Hangouts2Messages-SMS/hangouts_to_sms_er0sin/hangouts_parser.py",
	"owner": "_generated_diagnostic_collection_name_#0",
	"code": "E80",
	"severity": 8,
	"message": "can't assign to literal",
	"source": "Python (parser)",
	"startLineNumber": 25,
	"startColumn": 18,
	"endLineNumber": 25,
	"endColumn": 53
}
{
	"resource": "/c:/Users/USERNAME/odrive/Google Drive/Random/Hangouts2Messages-SMS/hangouts_to_sms_er0sin/hangouts_parser.py",
	"owner": "_generated_diagnostic_collection_name_#0",
	"code": "E16",
	"severity": 8,
	"message": "unexpected token '='",
	"source": "Python (parser)",
	"startLineNumber": 25,
	"startColumn": 53,
	"endLineNumber": 25,
	"endColumn": 54
}
{
	"resource": "/c:/Users/USERNAME/odrive/Google Drive/Random/Hangouts2Messages-SMS/hangouts_to_sms_er0sin/hangouts_parser.py",
	"owner": "_generated_diagnostic_collection_name_#0",
	"code": "E16",
	"severity": 8,
	"message": "unexpected token ')'",
	"source": "Python (parser)",
	"startLineNumber": 25,
	"startColumn": 61,
	"endLineNumber": 25,
	"endColumn": 62
}
{
	"resource": "/c:/Users/USERNAME/odrive/Google Drive/Random/Hangouts2Messages-SMS/hangouts_to_sms_er0sin/hangouts_parser.py",
	"owner": "_generated_diagnostic_collection_name_#0",
	"code": "E16",
	"severity": 8,
	"message": "unexpected token 'data_file'",
	"source": "Python (parser)",
	"startLineNumber": 25,
	"startColumn": 66,
	"endLineNumber": 25,
	"endColumn": 75
}
{
	"resource": "/c:/Users/USERNAME/odrive/Google Drive/Random/Hangouts2Messages-SMS/hangouts_to_sms_er0sin/hangouts_parser.py",
	"owner": "_generated_diagnostic_collection_name_#0",
	"code": "E16",
	"severity": 8,
	"message": "unexpected token ':'",
	"source": "Python (parser)",
	"startLineNumber": 25,
	"startColumn": 75,
	"endLineNumber": 25,
	"endColumn": 76
}
{
	"resource": "/c:/Users/USERNAME/odrive/Google Drive/Random/Hangouts2Messages-SMS/hangouts_to_sms_er0sin/hangouts_parser.py",
	"owner": "_generated_diagnostic_collection_name_#0",
	"code": "E32",
	"severity": 8,
	"message": "unexpected indent",
	"source": "Python (parser)",
	"startLineNumber": 27,
	"startColumn": 13,
	"endLineNumber": 27,
	"endColumn": 17
}
{
	"resource": "/c:/Users/USERNAME/odrive/Google Drive/Random/Hangouts2Messages-SMS/hangouts_to_sms_er0sin/hangouts_parser.py",
	"owner": "_generated_diagnostic_collection_name_#0",
	"code": "E80",
	"severity": 8,
	"message": "can't assign to ErrorExpression",
	"source": "Python (parser)",
	"startLineNumber": 27,
	"startColumn": 13,
	"endLineNumber": 27,
	"endColumn": 17
}
{
	"resource": "/c:/Users/USERNAME/odrive/Google Drive/Random/Hangouts2Messages-SMS/hangouts_to_sms_er0sin/hangouts_parser.py",
	"owner": "_generated_diagnostic_collection_name_#0",
	"code": "E16",
	"severity": 8,
	"message": "'return' outside function",
	"source": "Python (parser)",
	"startLineNumber": 65,
	"startColumn": 9,
	"endLineNumber": 65,
	"endColumn": 15
}

Edit: Possibly important detail, the «Analyzing workspace, 8 items remaining» is taking it’s sweet time (about an hour at this point) of finishing it’s analysis. I have some quite large json files (300+MB) which it might be hanging on.