After updating a script from Python 2 to Python 3, I am now getting an 'ERROR 00539: Indentation Error: Unexpected indent , line 1' on a line in my script. The line is not indented, and I tried removing all spaces and also re-adding spaces (ensuring no tabs were used). I am not sure where the error is. The line ran without error using Python 2. This is the original line: arcpy . CalculateField_management ( SubLayer_pp_trans_GUJoin_UniqueSubs , "SUB1SUB2" , ' [SUB_1] + "," + [SUB_2] ' ) I've tried: arcpy . CalculateField_management ( SubLayer_pp_trans_GUJoin_UniqueSubs , "SUB1SUB2" , ' !SUB_1! +","+ !SUB_2! ' ) and (and various renditions of removing spaces) arcpy . CalculateField_management ( SubLayer_pp_trans_GUJoin_UniqueSubs , "SUB1SUB2" , ' [SUB_1] + "," + [SUB_2] ' ) with no luck. Any suggestions? Thanks!

did you add "PYTHON_9.3" in order to use python... as in arcpy . CalculateField_management ( inTable , fieldName , expression , "PYTHON_9.3") and I think the indentation may be the first space in your expression. In python ! marks replace [ and ] as field delimiters From the help topic for map and for Pro

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Calculate field expression for string concatenation - Python 3.5

TessOldemeyer

After updating a script from Python 2 to Python 3, I am now getting an 'ERROR 00539: Indentation Error: Unexpected indent <<expression>, line 1' on a line in my script. The line is not indented, and I tried removing all spaces and also re-adding spaces (ensuring no tabs were used). I am not sure where the error is. The line ran without error using Python 2.

This is the original line:

arcpy<SPAN class="punctuation token">.</SPAN>CalculateField_management <SPAN class="punctuation token">(</SPAN>SubLayer_pp_trans_GUJoin_UniqueSubs<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"SUB1SUB2"</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="string token">' [SUB_1] + "," + [SUB_2] '</SPAN><SPAN class="punctuation token">)</SPAN>‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN>

I've tried:

arcpy<SPAN class="punctuation token">.</SPAN>CalculateField_management<SPAN class="punctuation token">(</SPAN>SubLayer_pp_trans_GUJoin_UniqueSubs<SPAN class="punctuation token">,</SPAN><SPAN class="string token">"SUB1SUB2"</SPAN><SPAN class="punctuation token">,</SPAN><SPAN class="string token">' !SUB_1! +","+ !SUB_2! '</SPAN><SPAN class="punctuation token">)</SPAN>‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN>

and (and various renditions of removing spaces)

arcpy<SPAN class="punctuation token">.</SPAN>CalculateField_management<SPAN class="punctuation token">(</SPAN>SubLayer_pp_trans_GUJoin_UniqueSubs<SPAN class="punctuation token">,</SPAN><SPAN class="string token">"SUB1SUB2"</SPAN><SPAN class="punctuation token">,</SPAN><SPAN class="string token">' [SUB_1] + "," + [SUB_2] '</SPAN><SPAN class="punctuation token">)</SPAN>‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN>

with no luck. Any suggestions?

Thanks!

Find more posts tagged with

Accepted answers

DanPatterson_Retired

did you add "PYTHON_9.3" in order to use python... as in

<SPAN>arcpy</SPAN><SPAN>.</SPAN><SPAN>CalculateField_management</SPAN><SPAN>(</SPAN><SPAN>inTable</SPAN><SPAN>,</SPAN> <SPAN>fieldName</SPAN><SPAN>,</SPAN> <SPAN>expression</SPAN><SPAN>,</SPAN> <SPAN>"PYTHON_9.3")</SPAN>

and I think the indentation may be the first space in your expression. In python ! marks replace [ and ] as field delimiters From the help topic for map and for Pro

All comments

TessOldemeyer

Agreed. For some reason, I do not have the 'Mark as Correct' option. I am viewing the discussion in All Places > Developers > GIS Developers > Python > Discussions in Chrome. I have also tried accessing it from both the email notification link and from my profile. I am logged in. I also referred to this document, and the button is not showing up on my discussion screen as shown.

...I don't remember the button not showing up for past discussions and have used it frequently in the past. Maybe I'm missing something. I apologize for any inconveniences.

Hornbydd

gardta‌you should mark Dan's answer as correct. It shows others a solution was found and acknowledges Dan's help.

TessOldemeyer

This seemed to do the trick. Thanks!

arcpy<SPAN class="punctuation token">.</SPAN>CalculateField_management<SPAN class="punctuation token">(</SPAN>SubLayer_pp_trans_GUJoin_UniqueSubs<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"SUB1SUB2"</SPAN><SPAN class="punctuation token">,</SPAN><SPAN class="string token">'!SUB_1! + "," + !SUB_2!'</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"PYTHON_9.3"</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN>

DanPatterson_Retired

did you add "PYTHON_9.3" in order to use python... as in

<SPAN>arcpy</SPAN><SPAN>.</SPAN><SPAN>CalculateField_management</SPAN><SPAN>(</SPAN><SPAN>inTable</SPAN><SPAN>,</SPAN> <SPAN>fieldName</SPAN><SPAN>,</SPAN> <SPAN>expression</SPAN><SPAN>,</SPAN> <SPAN>"PYTHON_9.3")</SPAN>

and I think the indentation may be the first space in your expression. In python ! marks replace [ and ] as field delimiters From the help topic for map and for Pro

TessOldemeyer

I did switch from ArcMap to Pro. It sounds like Python expressions would be best. Makes sense. Thanks!

bixb0012

Did you switch from ArcMap to Pro then?

I see that you are not passing an expression type, which means you are evaluating VB and not Python. Are you trying to work with VB or Python expressions?

The ArcGIS Pro Calculate Field—Data Management toolbox documentation has a note of caution about VB expressions:

Caution:
Field calculations with a VB Expression type are not supported on 64-bit products, including ArcGIS Pro, ArcGIS Desktop—Background Geoprocessing (64-bit)—and ArcGIS Server. To successfully use Calculate Field in these products, expressions should be converted to Python, or in the case of Background Geoprocessing (64-bit), background processing can alternatively be disabled.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.