Select to view content in your preferred language


12-31-2019 01:24 PM
MVP Emeritus

Python 2.7 Countdown 

Gone ... but not forgotten...

Any fond memories of the old ways?

Anything better about 2.7 versus 3.6/7/8?

You can relive the flame wars of ArcMap vs ArcGIS Pro.

Add your thoughts, especially if you didn't get the memo 10ish years ago when 3 came out

5 Replies
Occasional Contributor

RIP two seven. 

MVP Emeritus
0 Kudos
Regular Contributor

I missed all the drumroll action, I  guess. But it was about time,.

To me there have been a number of reasons to want to migrate sooner. I just enjoy working in the Jupyter environment and doing updates and dependency management with conda. Although the tool for managing separate versions have improved, I have found it only confusing to remember what version of arcpy to use for what. So let's embrace 3.x for good.

That being said, I'm sure next time I'm at an ESRI gig, someone will crack open 2.7 and start coding...

0 Kudos
New Contributor II

In 2.7 I liked that you didn't have to log in or have a stand alone license to use arcpy. I get the whole logging in to use ArcGIS python API but not the arcpy module. We had to run a command install with license pointing at a single use license to get task scheduler to run scripts under the SYSTEM account on our server. 

Tracy Wamsley

0 Kudos
MVP Emeritus

That isn't python's fault

0 Kudos