Analysis and Resolution of TypeError: bad operand type for unary +: 'str' in Python

Error Phenomenon and Background

During Python 2.7 development, programmers frequently encounter the TypeError: bad operand type for unary +: 'str' exception. This error typically occurs when attempting to apply the unary + operator to string types, indicating that the operand type does not meet the operator's expectations.

Problem Code Analysis

By examining the provided code example, we can identify the specific location where the error originates. In the stock data retrieval function, the following critical code segment exists:

print 'Pulled', + stock

This line intends to output "Pulled" followed by the stock code, but contains a serious syntactic issue. The developer incorrectly added the unary + operator after the comma, causing the Python interpreter to attempt a positive sign operation on the string variable stock.

Error Mechanism Deep Analysis

The unary + operator in Python is designed primarily for positive sign identification of numerical types, such as +5 representing positive five. When applied to strings, the Python interpreter cannot comprehend the meaning of this operation, thus throwing a type error exception.

From a syntactic perspective, print 'Pulled', + stock is actually parsed as:

• First argument of print statement: string 'Pulled'
• Second argument of print statement: expression + stock

Since stock is of string type, the expression + stock triggers type checking failure.

Correct Solution Approaches

According to best practices, there are two standard methods to correct this error:

Method 1: Using Comma-Separated Arguments

print 'Pulled', stock

This approach leverages the print statement's automatic handling of multiple arguments, which automatically adds space separation between parameters.

Method 2: Using String Concatenation

print 'Pulled ' + stock

This method uses the string concatenation operator + to combine two strings into a complete output string.

Related Error Pattern Extensions

Referencing other answers and supplementary materials, we observe that similar error patterns occur in other scenarios:

During URL construction, if the line continuation character \ is omitted, it may cause similar syntax errors:

urlToVisit = 'http://chartapi.finance.yahoo.com/instrument/1.0/'
+ stock + '/chartdata;type=quote;range=5d/csv'

In this case, the + stock on the second line would similarly be interpreted as unary operator application.

Another common error appears in user input processing:

height = input("How tall are you? ")
print( + height + " is a perfectly good height to be!")

The extra + symbol here also triggers type errors.

Type-Safe Programming Recommendations

To avoid such errors, developers are advised to:

1. Understand Operator Semantics: Clearly recognize that unary + operator only applies to numerical types
2. Code Review: Regularly inspect operator usage in code for correctness
3. Test Coverage: Write unit tests to verify proper string operations
4. Use Modern Python Versions: Python 3.x offers significant improvements in type checking and error messaging

Debugging Techniques and Best Practices

When encountering type errors, the following debugging strategies can be employed:

• Use type() function to verify variable types
• Add print statements at critical positions to examine variable values
• Utilize IDE syntax highlighting and error提示功能
• Read complete error stack traces to locate problem sources

Through systematic analysis and proper coding practices, developers can effectively avoid common errors like bad operand type for unary +: 'str', thereby improving code quality and development efficiency.