SAWarning causes memory leak

[nekto0n]

Hi there!
Interesting feature was discovered. When you supply queries with non-
unicode values you get this:
Unicode type received non-unicode bind param value
'ya37esbr24qhlu9kojf5z1x6m8gvinc0'

All warnings after being emitted go into the warning registry in order
to be able to ignore them in future. Registy is a dict, with key:
key = (text, category, lineno)

"text" is always different as you can see, so eventually - every
single warnings ends up being held in the registry, causing memory
leak. Wasn't sure if it's a bug or just nice feature - decided to
write here. Maybe it should be better to put 'value' somewhere else,
not in actual text?

[Michael Bayer]

wow that sucks does the warnings module document that ? we'd have to change that warning immediately.

> --
> You received this message because you are subscribed to the Google Groups "sqlalchemy" group.
> To post to this group, send email to sqlal...@googlegroups.com.
> To unsubscribe from this group, send email to sqlalchemy+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
>

[nekto0n]

warnings module documentation mentions that there's a registry, but
without any details...

[nekto0n]

To save some googling time. This message resulted in
http://www.sqlalchemy.org/trac/ticket/1822