Felix,
Another technique I have used, in case you are not aware of it:
I add this:
import traceback
util.warn(str(traceback.format_stack()))
to whichever sqlalchemy .py file is producing the error, right at the point
where the error is emitted. Then whenever it happens, you get a full stack
trace in the log. From here you can usually find out where in you app the
non-unicode string is coming from.
--bill
On Thu, Jan 10, 2013 at 1:37 AM, Felix Schwarz <[email protected]
> wrote:
>
> Am 10.01.2013 00:45, schrieb Michael Bayer:
> > Can't, because as a python warning, the "warnings" lib caches that
> message permanently, to support the typical case that the warnings filter
> is set to "once". If the message were unique for every value your app
> would slowly leak memory
>
> I see, bad luck. I'll continue to modify my SQLAlchemy ad hoc then.
>
> fs
>
> --
> You received this message because you are subscribed to the Google Groups
> "sqlalchemy" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/sqlalchemy?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sqlalchemy?hl=en.
