On Wed, Feb 24, 2010 at 03:25:50AM -0800, Paul Rigor (gmail) wrote: > What's affected: > 1) This cleans and removes a nice amount of code and helps focus on > optimizing how rows are fetched. > 2) Requires sqlalchemy which is fairly robust and well-maintained > 3) Forces users to explicitly specify RDBMs connection information instead > of relying on default configurations (eg, my.cnf, my.ini, etc).
Hi Paul, last time we talked about sqlalchemy inclusion, I couldn't get the tests working on my system. We never figured out what the problem was, but we should make sure that that problem doesn't pop up. I'm -1 on *requiring* sqlalchemy, in any case: each dependency is a real installation burden on people, especially while the packaging situation in Python is so problematic. (This is being fixed, but it will take a while.) I'd be happy to include sqlalchemy with pygr, or make it an optional dependency. And my test infrastructure supports testing it as an optional dependency, now (we'd have double the tests, but that's ok). cheers, --titus -- C. Titus Brown, c...@msu.edu -- You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-...@googlegroups.com. To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en.
