Nov 03
But sadly, it’s unusable for me. It really, really bums me out.
The bugs responsible are here and here. There’s related reading in Google Groups and also a related ticket here.
I want to put out a bounty for this bug, but I don’t want to step on the toes of the developers. Any fix that would be worth paying for would have to be one that the developers would approve of. I don’t even know what work might already be done on it. I guess I haven’t browsed the source yet to see what’s happening lately. That will be the next step.
Does anyone know if any work is being done on this? I have a few projects that I want to get started using Django, but this has taken the wind out of my sails. :(
November 4th, 2006 at 2:22 pm
Hey, I noticed in that first thread that Malcolm says it’s in his pile. You might like his comment in this thread.
November 6th, 2006 at 10:39 am
If you are getting caught up with Django’s ORM, might I suggest looking into pylons or TurboGears. Both work with SQLAlchemy, which is considered the most advanced python ORM. (Note that there was some talk a while back about django migrating to it (or allowing adapters to it)). It wouldn’t be too strange a year or two down the line to see features of TG, pylons and django converge a bit (sqlalchemy, genshi, routes, common wsgi-based middleware)