Timeline for Why does the next() method fail after the last record, using arcpy.da.SearchCursor?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2020 at 15:27 | history | edited | CommunityBot |
Commonmark migration
|
|
| Jan 15, 2018 at 10:25 | history | edited | PolyGeo♦ |
edited tags
|
|
| May 2, 2014 at 3:48 | history | tweeted | twitter.com/#!/StackGIS/status/462076048637980672 | ||
| May 1, 2014 at 23:29 | comment | added | Stephen Lead | @JasonScheirer maybe - but I didn't find anything when searching on arcpy.da.SearchCursor and next. I'm not an expert Python programmer so I didn't know to look up Python Iterator Protocol, etc. At least now it's available if someone searches on those keywords | |
| May 1, 2014 at 23:20 | comment | added | nickves | The line between spatial analysis and programming is very thin. | |
| May 1, 2014 at 23:14 | comment | added | Jason Scheirer | This is more a generic Python question that it is GIS-specific. I'm sorry this tripped you up at first, but it's behaving exactly like any reasonably designed API in Python would with regards to the iterator protocol. | |
| S May 1, 2014 at 22:47 | answer | added | Stephen Lead | timeline score: 4 | |
| S May 1, 2014 at 22:47 | history | asked | Stephen Lead | CC BY-SA 3.0 |