Right, but then a bunch of other errors (ImportWarning?!,
DeprecationWarning, etc) stop execution even reaching the code which
might be causing the SAWarning.
It's really quite disappointing that Python's warning mechanisms don't
report a full traceback...
On 15/09/2016 13:43, Mike Bayer wrote:
import warnings
warnings.simplefilter("error")
On 09/15/2016 08:07 AM, Chris Withers wrote:
Hi All,
How can I turn SAWarnings into exceptions?
I'm struggling with what to put into the PYTHONWARNINGS environment
variable :-S
cheers,
Chris
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
