Output messages from a script run within another script

Question

I apologize for the question, which must be redundant, but the search terms for a question like this are not very specific.

I have written several python scripts and imported them in ArcCatalog into a Toolbox.  They are all working fine.

Now I would like to call several of those tools from another script to simplify a process that is repeatable.  Using ImportToolbox I have successfully done this as well, but the output messages from the scripts that are being called are not visible - only the wrapper script's messages appear.  By "output", I mean messages that I print to the ArcCatalog tool console using gp.AddMessage.

What is the best practice for this?

KimOllivier · Answer

You might look at the standard logging module which handles calling other modules seamlessly, but still writes to a log file.

DarylVan_Dyke · Answer

This may help - I sometimes run into issues depending with printing when migrating scripts between 'run in ArcGIS python console', 'run in a Toolbox tool', and 'run in a stand-alone (CMD shell or IDLE) mode'.

This one was developed to run a log file (called fBad - because it's an error log).

So, read in your command arguments or over-ride and explictly set the path the log file:
if arcpy.GetParameterAsText(2):
    logBadData = arcpy.GetParameterAsText(2)
else:
    logBadData = "R:\test_pGDB"

###
#  Create Output Files
###
#output log Bad Data    
timeStamp = "2012_07_10"     # or whatever, use a function to stamp it!
fBad = open(logBadData+"_"+timeStamp+".txt",'w')

And now pass your error messages to the function
def tbxPrint(fBad,inStr):
    '''a general purpose function for try/except printing
    inside a toolbox function'''
    try:
        arcpy.AddMessage(inStr)
    except:
        print inStr
    finally:
        fBad.write(inStr+"
")

in a manner like
tbxPrint(fBad,"

Created "+PathAndNameGDB)
tbxPrint(fBad,"
       with log file "+logBadData+"
 
 ")

To save 5 characters you could use default arguments if you only had 1 log file, but I didn't, so there it is.  Just remember to close your file (or file-like object) at the end of the script as good practice.

Daryl

NathanSpears · Answer

I am familiar with modules in python but hadn't considered importing the functions directly.  I will try that out and get back to you.  Thanks for the idea!