Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #8528
| Date | 2011-06-28 03:09 -0500 |
|---|---|
| From | Andrew Berg <bahamutzero8825@gmail.com> |
| Subject | Re: Trying to chain processes together on a pipeline |
| References | <mailman.467.1309240659.1164.python-list@python.org> <iuc0oo$7dm$1@r03.glglgl.eu> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.473.1309248563.1164.python-list@python.org> (permalink) |
On 2011.06.28 02:44 AM, Thomas Rachel wrote:
> The way you work with the exception is not the very best - instead of
> parsing the stringified exception, you better would trigger on
> exc.winerror (it is an integer with the error number).
>
> Or, even better, just pas the error information contained in the exception:
>
> def handle_winerr(exc):
> logger.critical('Could not execute %s: %s' %
> (queue[position].sox_exe, exc.strerror))
I didn't see winerror and strerror in the docs before, but another look
and they are indeed documented. I brought up Windows error codes before,
and I'm surprised no one pointed this out. Thanks for that.
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Trying to chain processes together on a pipeline Andrew Berg <bahamutzero8825@gmail.com> - 2011-06-28 00:57 -0500
Re: Trying to chain processes together on a pipeline Thomas Rachel <nutznetz-0c1b6768-bfa9-48d5-a470-7603bd3aa915@spamschutz.glglgl.de> - 2011-06-28 09:44 +0200
Re: Trying to chain processes together on a pipeline Andrew Berg <bahamutzero8825@gmail.com> - 2011-06-28 03:09 -0500
csiph-web