Ryan & Alexandre, nice work so far! On Sat, May 23, 2009 at 05:22:36PM -0700, Ryan Boggs wrote: > So you are using Postgresql as you back end DB. Have you tried using > py-psycopg2 with Django? I've been using it for my testing without > problems and it doesn't seem to rely on py-mxDateTime.
So it's looking as if it's not, strictly speaking, Django's fault after all. > Still, even though removing py-mxDateTime allows Django 1.0+ to work, > that's not the desired work around to get into ports, right? The best solution would be to track this down to where the problem really lives and fix it or work around it there. This is the only "real" solution. However, is it true that Django is using mxDateTime with some odd usage pattern that triggers this? If so then perhaps a workaround might be found in Django itself. But I went fishing for maintainers because I lack time: I'm no longer a pig here. I'm barely a chicken. So I'll shut up and let you people keep at it. ;-) -- Darrin Chandler | Phoenix BSD User Group | MetaBUG [email protected] | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
