On Mon, 2007-11-19 at 08:50 -0800, MichaelMartinides wrote: > Hi James, > > I entirely understand your point. > > But for users as me, it makes a difference to know if a feature is in > very far distant or rather near future... > > I tried the branch it worked in command mode line as expected but gave > an error when I tried it in the browser, so I simply asked.
It's completely unready for testing. This is noted on the wiki page for the branch: http://code.djangoproject.com/wiki/QuerysetRefactorBranch Due to the very low-level technical nature of the changes, correctness at the SQL level is the first aim and *then* adjusting the rest of the code. So I wouldn't be testing it yet. As Karen said, end of the month is the rough target. It certainly won't be earlier than that, might be a bit later. Depends on how much Real Life I have between now and then. Malcolm -- Success always occurs in private and failure in full view. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
