Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #7763 > unrolled thread

Re: Trapping MySQLdb warnings

Started byTerry Reedy <tjreedy@udel.edu>
First post2011-06-16 15:40 -0400
Last post2011-06-16 15:40 -0400
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Trapping MySQLdb warnings Terry Reedy <tjreedy@udel.edu> - 2011-06-16 15:40 -0400

#7763 — Re: Trapping MySQLdb warnings

FromTerry Reedy <tjreedy@udel.edu>
Date2011-06-16 15:40 -0400
SubjectRe: Trapping MySQLdb warnings
Message-ID<mailman.37.1308253249.1164.python-list@python.org>
On 6/16/2011 3:01 PM, Tim Johnson wrote:
> * Terry Reedy<tjreedy@udel.edu>  [110616 10:50]:

>> The machinery in the warnings module is only for instances of
>> subsclasses of Warning. Are the warnings from MySQLdb properly such
>> objects? If so, what class are they?

>   The warnings are sent directly to stdout. No way that I know of to
>   find out what classes they are..

The doc for any python module 'should' tell you about custom exception 
and warning classes. Srinivas' says in his post MySQLdb.Exception and 
MySQLdb.Warning, which would be sensible.

-- 
Terry Jan Reedy

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web