Timeline for Updating Field to Calculated Variable using Arcpy
Current License: CC BY-SA 3.0
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 28, 2016 at 22:22 | comment | added | Michael Stimson | I'd laugh if I hadn't inadvertently done the same thing when I started using python... definitely a trap. Python doesn't give you error messages when you try to instantiate the same variable again like programming languages do. Like you said though the answer is to label your variables with uRow for update and sRow for search every time and get into the habit; there's seldom a need for two search, update or insert cursors at the same time. +1 for spotting this error yourself (trust me it's hard to find because there's nothing wrong with the syntax!) | |
| Apr 28, 2016 at 21:06 | history | answered | Owen P | CC BY-SA 3.0 |