Hi,

I've just been discussing Python's logging package with Armin Ronacher
of Pocoo over on stdlib-sig:

http://mail.python.org/pipermail/stdlib-sig/2009-September/000671.html

In that post, Armin says that the SQLAlchemy development team had a
lot of problems with Python logging and had to do an "Incredible
dance" relating to loggers for temporary database connections.

I like dancing as much as the next guy, and the more incredible the
better, but *unnecessary* incredible dancing is a different thing
altogether ;-)

Seriously, as the author of the logging package, I'm sorry if you've
had any problems with logging, and I'm reasonably responsive to issues
raised on Python's bug tracker. I don't recall seeing anything from
the SQLAlchemy developers,but I could have missed it.

Can someone enlighten me as to the specifics of these problems, and
what I can do to help?

Thanks and regards,

Vinay Sajip

P.S. I think SQLAlchemy is great!

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

Reply via email to