I often write the results of geoprocessing scripts to a text file. After doing some research, I learned I'm not using best practices for closing the file. I'm not opening the file using the with keyword, so the file may not close if there is an error. If there is an error, I need to be able to write the error message to the text file. It looks like I could use the finally keyword or with keyword to ensure the file closes. Which of these options is better? And if I've made any errors in how I think I could improve my implementation, please let me know. Thanks! Method #1 try : # log file to write to logFile = r 'path\tofile\fileName.txt' # open file in write mode report = open ( logFile , 'w' ) # geoprocessing stuff # write to report report . write ( 'some message' ) except Exception as e : # get line number and error message report . write ( 'an error message' ) finally : report . close ( ) Method #2 try : # log file to write to logFile = r 'path\tofile\fileName.txt' # open file in write mode with open ( logFile , 'w' ) as f : # geoprocessing stuff # write to report f . write ( 'some message' ) except Exception as e : # get line number and error message with open ( logFile , 'a' ) as f : f . write ( 'an error message' )

It seems like there are several possible error states you want to handle here: * LogFile does not exist when trying to write to it * Error thrown in 'Geoprocessing Stuff' section For the first point, the mode argument in open() can include a '+' character which will cause the file to be created if it doesn't exist. If the directory itself doesn't exist then you'll see a FileNotFoundException. This can be handled as such: try : f = open ( log_file , 'a+' ) # use 'a+' to append, 'w+' to truncate except FileNotFoundException : # handle the file system issues Then for the second point, you'd want to handle the Geoprocessing Errors inside the with block as such: with f : log_msg = "" try : # Geoprocessing Stuff log_msg += do_gp_stuff_step1 ( ) log_msg += do_gp_stuff_step2 ( ) log_msg += 'Success!' except Exception as e : # Be more specific based on your code log_msg += e finally : # Clean up Geoprocessing stuff f . write ( log_msg ) Obviously you'd want to make things more readable with string formatting, or can build log_msg in other ways, but this is the basic pattern that I would recommend.

I had to look up OP to confirm you were referring to me. My scripts bail if there is an error. My scripts are doing things like rebuilding address locators, rebuilding tiles for cached services, running replication, etc. I basically want to know if the task ran successful or not. If it failed, that is okay, I just want to know why it failed.

That's true, bixb0012 There are indeed many ways to solve this puzzle. I know in our scheduled task scripts we do both ways (bail immediately or try to continue) depending on the script.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What is Best Way to Handle Files in Python

pmckinney

I often write the results of geoprocessing scripts to a text file. After doing some research, I learned I'm not using best practices for closing the file. I'm not opening the file using the with keyword, so the file may not close if there is an error. If there is an error, I need to be able to write the error message to the text file. It looks like I could use the finally keyword or with keyword to ensure the file closes.

Which of these options is better? And if I've made any errors in how I think I could improve my implementation, please let me know. Thanks!

Method #1

<SPAN class="keyword token">try</SPAN><SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp; <SPAN class="comment token"># log file to write to</SPAN>
&nbsp;&nbsp; logFile <SPAN class="operator token">=</SPAN> r<SPAN class="string token">'path\tofile\fileName.txt'</SPAN>

&nbsp;&nbsp; <SPAN class="comment token"># open file in write mode</SPAN>
&nbsp;&nbsp; report <SPAN class="operator token">=</SPAN> open<SPAN class="punctuation token">(</SPAN>logFile<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">'w'</SPAN><SPAN class="punctuation token">)</SPAN>

&nbsp;&nbsp; <SPAN class="comment token"># geoprocessing stuff</SPAN>

&nbsp;&nbsp; <SPAN class="comment token"># write to report</SPAN>
&nbsp;&nbsp; report<SPAN class="punctuation token">.</SPAN>write<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'some message'</SPAN><SPAN class="punctuation token">)</SPAN>

<SPAN class="keyword token">except</SPAN> Exception <SPAN class="keyword token">as</SPAN> e<SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp; <SPAN class="comment token"># get line number and error message</SPAN>
&nbsp;&nbsp; report<SPAN class="punctuation token">.</SPAN>write<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'an error message'</SPAN><SPAN class="punctuation token">)</SPAN>

<SPAN class="keyword token">finally</SPAN><SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp; report<SPAN class="punctuation token">.</SPAN>close<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Method #2

<SPAN class="keyword token">try</SPAN><SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp; <SPAN class="comment token"># log file to write to</SPAN>
&nbsp;&nbsp; logFile <SPAN class="operator token">=</SPAN> r<SPAN class="string token">'path\tofile\fileName.txt'</SPAN>
&nbsp;&nbsp; 
&nbsp;&nbsp; <SPAN class="comment token"># open file in write mode</SPAN>
&nbsp;&nbsp; <SPAN class="keyword token">with</SPAN> open<SPAN class="punctuation token">(</SPAN>logFile<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">'w'</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="keyword token">as</SPAN> f<SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="comment token"># geoprocessing stuff</SPAN>
&nbsp;&nbsp; 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="comment token"># write to report</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; f<SPAN class="punctuation token">.</SPAN>write<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'some message'</SPAN><SPAN class="punctuation token">)</SPAN>

<SPAN class="keyword token">except</SPAN> Exception <SPAN class="keyword token">as</SPAN> e<SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp; <SPAN class="comment token"># get line number and error message</SPAN>
&nbsp;&nbsp; <SPAN class="keyword token">with</SPAN> open<SPAN class="punctuation token">(</SPAN>logFile<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">'a'</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="keyword token">as</SPAN> f<SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; f<SPAN class="punctuation token">.</SPAN>write<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'an error message'</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Encontre mais publicações marcadas com

Accepted answers

All comments

JoshuaBixby

Are you expecting to run into errors writing results out to file, or are you looking to write geoprocessing errors you find to a file?

blake.terhune

I don't see any reason why you would not want to use the with statement when working with files. Our organization does similar to method #2 for our own scheduled task script logging, although I write the data to a table in our enterprise geodatabase rather than a text file.

pmckinney

I write geoprocessing (Exception) and other (Environment Errors) errors to the text file. The scripts are set as scheduled tasks, so I like to keep tabs on whether they are successful or not.

pmckinney

Am I correct in thinking that using the with keyword, I will need to open the text file in the try statement and any except statements I have?

blake.terhune

Using the with keyword to open the text file only acts as a try/finally block just for that file. It doesn't handle exceptions. Using the with inside the try/except like Method #2 allows you to write the success or failure of the script. Alternatively, you could do something like...

<SPAN class="keyword token">try</SPAN><SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">=</SPAN> <SPAN class="string token">""</SPAN>
&nbsp;&nbsp;&nbsp; do something useful
&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">+=</SPAN> <SPAN class="string token">"something useful completed\n"</SPAN>
&nbsp;&nbsp;&nbsp; do something special
&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">+=</SPAN> <SPAN class="string token">"something special completed\n"</SPAN>

<SPAN class="keyword token">except</SPAN> Exception <SPAN class="keyword token">as</SPAN> err<SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">+=</SPAN> str<SPAN class="punctuation token">(</SPAN>err<SPAN class="punctuation token">)</SPAN>

<SPAN class="keyword token">finally</SPAN><SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="keyword token">try</SPAN><SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="keyword token">with</SPAN> open<SPAN class="punctuation token">(</SPAN>logFile<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">'a'</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="keyword token">as</SPAN> f<SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; f<SPAN class="punctuation token">.</SPAN>write<SPAN class="punctuation token">(</SPAN>log_msg<SPAN class="punctuation token">)</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="keyword token">except</SPAN> Exception<SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="keyword token">pass</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

This would allow you to log success and failure messages and only deal with writing to the log file once. The with is also put inside a try/except, allowing any other cleanup code in the finally block to actually finish in case something goes wrong when trying to write to the log file.

JoshuaBixby

Not to ask yet another question, but I am trying to understand the overall workflow a bit better. Are either of the 2 blocks of code above within a larger loop or is there a loop or sequence of processing that happens in the "geoprocessing stuff" block.

pmckinney

The general flow of the scripts are:

1. Import modules

2. Get the current date in the m-d-y format

3. Enter try statement

4. Open log file in write mode

5. Run geoprocessing tool(s)

6. Write results messages to log file

7. Enter except Environment Error statement

8. capture line number of error and error message

9. Write line number and error message to log file

7. Enter except Exception statement

8. capture line number of error and error message

9. Write line number and error message to log file

10. close the log file

JoshuaBixby

Blake Terhune‌, your code snippet does raise a question/issue:

<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> <SPAN class="keyword token">try</SPAN><SPAN class="punctuation token">:</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">=</SPAN> <SPAN class="string token">""</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; int<SPAN class="punctuation token">(</SPAN>None<SPAN class="punctuation token">)</SPAN> <SPAN class="comment token"># do something that causes error</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">+=</SPAN> <SPAN class="string token">"something useful completed\n"</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; int<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'1'</SPAN><SPAN class="punctuation token">)</SPAN>&nbsp; <SPAN class="comment token"># do something that works</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">+=</SPAN> <SPAN class="string token">"something useful completed\n"</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; 
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN> <SPAN class="keyword token">except</SPAN> Exception <SPAN class="keyword token">as</SPAN> err<SPAN class="punctuation token">:</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">+=</SPAN> err<SPAN class="punctuation token">.</SPAN>message
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; 
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN> <SPAN class="keyword token">finally</SPAN><SPAN class="punctuation token">:</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="keyword token">print</SPAN> log_msg
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; 
int<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN> argument must be a string <SPAN class="operator token">or</SPAN> a number<SPAN class="punctuation token">,</SPAN> <SPAN class="operator token">not</SPAN> <SPAN class="string token">'NoneType'</SPAN>
<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> <SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Does the OP want the processing to stop completely when an error occurs? I don't know. I am still trying to sort out whether the OP wants to bail or continue on:

<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> log_msg <SPAN class="operator token">=</SPAN> <SPAN class="string token">""</SPAN>
<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> <SPAN class="keyword token">try</SPAN><SPAN class="punctuation token">:</SPAN>&nbsp; 
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; int<SPAN class="punctuation token">(</SPAN>None<SPAN class="punctuation token">)</SPAN> <SPAN class="comment token"># do something that causes error</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">+=</SPAN> <SPAN class="string token">"something useful completed\n"</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN> <SPAN class="keyword token">except</SPAN> Exception <SPAN class="keyword token">as</SPAN> err<SPAN class="punctuation token">:</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">+=</SPAN> err<SPAN class="punctuation token">.</SPAN>message <SPAN class="operator token">+</SPAN> <SPAN class="string token">"\n"</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN> <SPAN class="keyword token">try</SPAN><SPAN class="punctuation token">:</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; int<SPAN class="punctuation token">(</SPAN><SPAN class="string token">'1'</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="comment token"># # do something that works</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">+=</SPAN> <SPAN class="string token">"something useful completed\n"</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN> <SPAN class="keyword token">except</SPAN> Exception <SPAN class="keyword token">as</SPAN> err<SPAN class="punctuation token">:</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN>&nbsp;&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">+=</SPAN> err<SPAN class="punctuation token">.</SPAN>message <SPAN class="operator token">+</SPAN> <SPAN class="string token">"\n"</SPAN>
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN> <SPAN class="keyword token">print</SPAN> log_msg
<SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN><SPAN class="punctuation token">.</SPAN> 
int<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN> argument must be a string <SPAN class="operator token">or</SPAN> a number<SPAN class="punctuation token">,</SPAN> <SPAN class="operator token">not</SPAN> <SPAN class="string token">'NoneType'</SPAN>
something useful completed

<SPAN class="operator token">>></SPAN><SPAN class="operator token">></SPAN> <SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

ClintonDow1

It seems like there are several possible error states you want to handle here:

LogFile does not exist when trying to write to it
Error thrown in 'Geoprocessing Stuff' section

For the first point, the mode argument in open() can include a '+' character which will cause the file to be created if it doesn't exist. If the directory itself doesn't exist then you'll see a FileNotFoundException. This can be handled as such:

<SPAN class="keyword token">try</SPAN><SPAN class="punctuation token">:</SPAN>
&nbsp; f <SPAN class="operator token">=</SPAN> open<SPAN class="punctuation token">(</SPAN>log_file<SPAN class="punctuation token">,</SPAN> <SPAN class="string token">'a+'</SPAN><SPAN class="punctuation token">)</SPAN>&nbsp;&nbsp; <SPAN class="comment token"># use 'a+' to append, 'w+' to truncate</SPAN>
<SPAN class="keyword token">except</SPAN> FileNotFoundException<SPAN class="punctuation token">:</SPAN>
&nbsp; <SPAN class="comment token"># handle the file system issues</SPAN>
‍‍‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Then for the second point, you'd want to handle the Geoprocessing Errors inside the with block as such:

<SPAN class="keyword token">with</SPAN> f<SPAN class="punctuation token">:</SPAN>
&nbsp; log_msg <SPAN class="operator token">=</SPAN> <SPAN class="string token">""</SPAN>
&nbsp; <SPAN class="keyword token">try</SPAN><SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="comment token"># Geoprocessing Stuff</SPAN>
&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">+=</SPAN> do_gp_stuff_step1<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>
&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">+=</SPAN> do_gp_stuff_step2<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>
&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">+=</SPAN> <SPAN class="string token">'Success!'</SPAN>
&nbsp; <SPAN class="keyword token">except</SPAN> Exception <SPAN class="keyword token">as</SPAN> e<SPAN class="punctuation token">:</SPAN>&nbsp; <SPAN class="comment token"># Be more specific based on your code</SPAN>
&nbsp;&nbsp;&nbsp; log_msg <SPAN class="operator token">+=</SPAN> e
&nbsp; <SPAN class="keyword token">finally</SPAN><SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="comment token"># Clean up Geoprocessing stuff </SPAN>
&nbsp;&nbsp;&nbsp; f<SPAN class="punctuation token">.</SPAN>write<SPAN class="punctuation token">(</SPAN>log_msg<SPAN class="punctuation token">)</SPAN>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Obviously you'd want to make things more readable with string formatting, or can build log_msg in other ways, but this is the basic pattern that I would recommend.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.