We're getting pretty close to merging queryset-refactor into trunk and would like to do this as soon as practical. There are still a couple of enhancements to add (#5420, mostly), one bug to fix (#5937) and some internal tweaking to do, but all the main stuff is ready to be used.
So if anybody wants to test it out, go ahead. Read the wiki page[1] if you've got code that does any slightly unusual stuff, but for existing code that works on trunk, there shouldn't be any real changes required. [1] http://code.djangoproject.com/wiki/QuerysetRefactorBranch File any bug reports in Trac against the queryset-refactor "version" (please do NOT put the qs-rf keyword on the ticket; I'm using that for other purposes). Bug reports that are regressions from existing functionality are more interesting and important at the moment than feature enhancements to the new features, since the latter case can be dealt with at our leisure (they're not features that people are already relying upon). If you see any different results testing against the branch compared to trunk, it would be interesting to know about them. Reduce it to a small example before opening a ticket, wherever possible. Please don't make me wade through dozens of lines of code just to get to one query that is relevant. Bear in mind, though, that the difference could be because a bug existed in trunk and the branch is now giving the correct result. So make sure your test case is valid (even I got bitten by that in a project I wrote). Regards, Malcolm -- The sooner you fall behind, the more time you'll have to catch up. 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 -~----------~----~----~----~------~----~------~--~---
