Migrating Python 2.7 From Desktop to 3.1 for Pro

Question

We've been running ArcGIS Desktop with Python 2.7 and intend to migrate to ArcGIS Pro with Python 3.1 before the switchover in April:

1. Can Modelbuilder import Python scripts and make a model based on the scripts if they run successfully using the runtime of ArcGIS Desktop?

2. Can Python 2.7 scripts be migrated to ArcGIS Pro without editing, or are there syntax differences to be aware of?

3. Can MXDs with shapefiles be migrated easily from one platform to the next?  Are there any significant syntax differences in the operands of each Arc platform?

danretired · Answer

These work

c:\temp\poly.png
c:/temp/poly.png
r"c:	emp\poly.png"

arcpy.env.workspace = r"c:	emp"
image_file = "{}".format(arcpy.env.workspace) + r"\poly.png"

image_file
'c:\Temp\poly.png'

image_file = rf"{arcpy.env.workspace}" + r"\poly.png"

image_file
'c:\Temp\poly.png'

1, 2 ... windows, "linux"

3 .... "raw" format

5,6,  and 5,11  two variants of "f-string" formatting

Cartographer7 · Answer

A few others thing that is sort of confusing is that the Python has an

https://pro.arcgis.com/en/pro-app/3.1/arcpy/get-started/setting-paths-to-data.htm

\ versus \ standard

It seems when you do do an 'r' command you use a single slash.

When you just declare a path is what a variable is equal to, you use a \

1. Is that correct?

2. I also noticed you can specify a path as the env.workspace, as your Windows path you are referring to.

but it appears that you can't use it as a tack on variable when doing a read.

so   placeholdervariableforshapedotshp= r+env.workspace+"\shapefiles\shape.shp" won't work because the env.workspace is declared with \

I had tried to create an renvworkspace =  pathtoworkspace described with single slashes, and that doesn't appear to work either.

Can you tell me where I am assuming wrong?

danretired · Answer

Every tool, under Parameters, has a Dialog and python tab

Spatial Join (Analysis)—ArcGIS Pro | Documentation

code examples are in the python tab