Analysis and Solution for Python Script Execution Error: From 'import: command not found' to Executable Scripts

Problem Background and Error Analysis

In Python development, developers frequently encounter script execution errors, with 'import: command not found' being a typical initial issue. This error commonly occurs when attempting to execute a Python script file directly, as the system fails to recognize the Python syntax within the script. From a technical perspective, the core of this error lies in the operating system's inability to interpret the first line of code in the script file.

In-depth Analysis of Error Causes

When a user executes the ./xx.py command in the terminal, the system attempts to run the file directly. However, if the file lacks a proper shebang line (i.e., #!/usr/bin/python), the system defaults to using the shell to execute the file content. Since the shell cannot understand Python's import statement, it produces the 'command not found' error.

Comparing the following two execution methods provides clearer insight into this issue:

# Incorrect method: direct execution (missing shebang line)
./xx.py
# Output: ./xx.py: line 1: import: command not found

# Correct method: execution via Python interpreter
python xx.py
# Executes Python code normally

Complete Solution

To resolve this issue, two aspects must be addressed: adding the correct shebang line and ensuring the file has executable permissions.

Step 1: Add Shebang Line

Add the following content at the first line of the Python script:

#!/usr/bin/python
import urllib2, base64

# Subsequent code remains unchanged
request = urllib2.Request("http://api.foursquare.com/v1/user")
base64string = base64.encodestring('%s:%s' % (username, password)).replace('\n', '')
request.add_header("Authorization", "Basic %s" % base64string)
result = urllib2.urlopen(request)

Step 2: Set File Permissions

Execute the following command in the terminal:

chmod +x xx.py

Step 3: Verify Execution

Now the script can be executed directly:

./xx.py

Technical Principles Explained

The shebang line specifies the script's interpreter. When the system executes a file, it examines the first two bytes. If these bytes are #!, the system reads the remainder of the line as the interpreter path and uses that interpreter to execute the script content.

For Python scripts, common shebang line formats include:

#!/usr/bin/python          # Uses system default Python
#!/usr/bin/env python     # Uses Python from environment variables
#!/usr/bin/python3        # Explicitly specifies Python 3 version

Advanced Considerations and Best Practices

1. Python Version Compatibility: If the script needs to run under different Python versions, it is advisable to use #!/usr/bin/env python, which automatically utilizes the Python interpreter in the current environment.

2. Improved Error Handling: The authentication portion of the original code can be further optimized by adding exception handling:

#!/usr/bin/python
import urllib2, base64
import sys

try:
    request = urllib2.Request("http://api.foursquare.com/v1/user")
    base64string = base64.encodestring('%s:%s' % (username, password)).replace('\n', '')
    request.add_header("Authorization", "Basic %s" % base64string)
    result = urllib2.urlopen(request)
    print("Authentication successful")
except urllib2.URLError as e:
    print("URL error:", e.reason)
except Exception as e:
    print("Other error:", str(e))

3. Environment Variable Configuration: Ensure the Python interpreter path is included in the system's PATH environment variable, which is a prerequisite for #!/usr/bin/env python to function correctly.

Common Issue Troubleshooting

If issues persist after adding the shebang line, follow these troubleshooting steps:

1. Verify there are no spelling errors in the shebang line
2. Check that file permissions are correctly set
3. Confirm the Python interpreter path exists
4. Use the file xx.py command to check file type
5. Use which python to confirm Python interpreter location

Through this comprehensive analysis and solution set, developers can completely resolve the 'import: command not found' error and create robust executable Python scripts.