Latest Contributions by BlakeTerhune

In Python 3 (ArcGIS Pro) this is what I typically do, mostly to track where errors occur so I can more easily troubleshoot to data. Especially if this update cursor work is in a separate function than your main code.   with arcpy.da.UpdateCursor("myFeatureClass", ["someUniqueID", "Field1", "Field2"]) as uCursor: for uid, field1, field2 in uCursor: try: # Do some business logic. field2 = field1 * 100 # Commit new values to table. # To throw an error with the cursor: # use a value that does not conform to your field type # or change the number of values in the row. uCursor.updateRow([uid, field1, field2, "thisWillError"]) except Exception as e: raise Exception(f"Error updating row at someUniqueID {uid}") from e   If you want the most coverage possible, following the "suggestions" in the documentation, I suppose you could do something like this (though I never have). with arcpy.da.UpdateCursor("AnchorPoints", ["someUniqueID", "Field1", "Field2"]) as uCursor: try: for uid, field1, field2 in uCursor: try: # Do some business logic. field2 = field1 * 100 # Commit new values to table. uCursor.updateRow([uid, field1, field2]) except Exception as e: raise Exception(f"Error updating row at someUniqueID {uid}") from e finally: del uCursor As for having an incorrect field name, the cursor will fail to be created so there's no cursor object to delete. In that case, you would have to follow the suggestion in the documentation and have it in a separate function so the everything gets cleaned up with garbage collection when it goes out of scope on exit (regardless of an exception). That's pretty tedious though. You might need to contact Esri support about the behavior your seeing when the cursor fails. ... View more