2008/5/29 <[EMAIL PROTECTED]>: >> * I have moved the common functions I was using to display messages to >> misc.py along with my special exception object. > > I found myself doing something similar for another error-handling > exception object that I've written as part of some of the upcoming > filelist changes. I'm wondering if there's an opportunity here to > create a module for common error handling routines; however, I'm not > exactly sure if that's required yet. Do you have any thoughts?
I would very much like to see us adopt a common set of error-handling routines. I'm also not certain that I really picked the best names for the routines I created. My intent was just to create something that was a few characters and easily recognisable. I think these changes could be integrated and then once your filelist changes are putback a common interface could created from the merge of the two. >> Once in a while you'll see an error from the shell about resource >> unavailable, but no python tracebacks best I can tell. > > Somebody just filed this as 2083. Do you know if this is related to > SIGPIPE or something different? I haven't had a chance to debug this > yet, and the bug report lacked a fair amount of detail. It isn't related to EPIPE. Best I can tell; the error is EAGAIN. My hunch is that something is printing out the error along the way and shouldn't be or there's a socket connection that we attempt to close that is already out of scope. I planned on looking at bug 2083 tonight to see what was actually causing the error. I know for certain that it isn't the exception handling in client.py; I have researched that far. Cheers, -- Shawn Walker "To err is human -- and to blame it on a computer is even more so." - Robert Orben _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
