=== RESPONSE to Answers/Comments in post ====== RESPONSE to Answers/Comments in post ===
So basically it handshangs on the df list. There is no further error message even if you try to capture it.
and directory structure
##Issue with modified script from Polygeo === END Response ===Same problems.
=== END Response ===
=== RESPONSE to Answers/Comments in post ===
So basically it hands on the df list. There is no further error message even if you try to capture it.
and directory structure
=== END Response ===
=== RESPONSE to Answers/Comments in post ===
So basically it hangs on the df list. There is no further error message even if you try to capture it.
and directory structure
##Issue with modified script from Polygeo Same problems.
=== END Response ===
=== RESPONSE to Answers/Comments in post ===
Messages
Executing: InvestigateMXDs P:\2012\096_CCRC_2_Biodiversity\Working\BiodiversityOverlay_70k_Series3b.mxd D:\junk
Start Time: Mon Aug 06 09:01:22 2012
Running script InvestigateMXDs...
Now processing ...
Map: P:\2012\096_CCRC_2_Biodiversity\Working\BiodiversityOverlay_70k_Series3b.mxd
So basically it hands on the df list. There is no further error message even if you try to capture it.
Test on simple mxd is below. Note that this works fine when run as a python script directly.
Messages
Executing: InvestigateMXDs P:\2012\183_TownPlanning_Symbology\Working\test.mxd P:\2012\183_TownPlanning_Symbology\Working\junk
Start Time: Tue Aug 07 09:11:35 2012
Running script InvestigateMXDs...
Now processing ...
Map: P:\2012\183_TownPlanning_Symbology\Working\test.mxd
When run as a python we get the following in less than 30s
starting...['test.mxd']
working on 1...<geoprocessing Map object object at 0x029471E0>P:\2012\183_TownPlanning_Symbology\Working\test
working on 2...[<DataFrame object at 0xee12950[0xee22fc0]>]P:\2012\183_TownPlanning_Symbology\Working\test
working on 3...in: P:\2012\183_TownPlanning_Symbology\Working\test\Layers
TRC_Boundary is visible PROCESSING...
TRC_Boundary is not visible. Not Processing
Map_Extents is visible PROCESSING...
Map_Extents is not visible. Not Processing
and directory structure
=== END Response ===
=== RESPONSE to Answers/Comments in post ===
Messages
Executing: InvestigateMXDs P:\2012\096_CCRC_2_Biodiversity\Working\BiodiversityOverlay_70k_Series3b.mxd D:\junk
Start Time: Mon Aug 06 09:01:22 2012
Running script InvestigateMXDs...
Now processing ...
Map: P:\2012\096_CCRC_2_Biodiversity\Working\BiodiversityOverlay_70k_Series3b.mxd
So basically it hands on the df list. There is no further error message even if you try to capture it.
Test on simple mxd is below. Note that this works fine when run as a python script directly.
Messages
Executing: InvestigateMXDs P:\2012\183_TownPlanning_Symbology\Working\test.mxd P:\2012\183_TownPlanning_Symbology\Working\junk
Start Time: Tue Aug 07 09:11:35 2012
Running script InvestigateMXDs...
Now processing ...
Map: P:\2012\183_TownPlanning_Symbology\Working\test.mxd
When run as a python we get the following in less than 30s
starting...['test.mxd']
working on 1...<geoprocessing Map object object at 0x029471E0>P:\2012\183_TownPlanning_Symbology\Working\test
working on 2...[<DataFrame object at 0xee12950[0xee22fc0]>]P:\2012\183_TownPlanning_Symbology\Working\test
working on 3...in: P:\2012\183_TownPlanning_Symbology\Working\test\Layers
TRC_Boundary is visible PROCESSING...
TRC_Boundary is not visible. Not Processing
Map_Extents is visible PROCESSING...
Map_Extents is not visible. Not Processing
and directory structure
=== END Response ===