Message from discussion
Feel free to test queryset-refactor branch
Received: by 10.35.90.4 with SMTP id s4mr7699226pyl.5.1208085824238;
Sun, 13 Apr 2008 04:23:44 -0700 (PDT)
Return-Path: <malc...@pointy-stick.com>
Received: from tallyho.bytemark.co.uk (tallyho.bytemark.co.uk [80.68.81.166])
by mx.google.com with ESMTP id z53si2438261pyg.1.2008.04.13.04.23.43;
Sun, 13 Apr 2008 04:23:44 -0700 (PDT)
Received-SPF: neutral (google.com: 80.68.81.166 is neither permitted nor denied by best guess record for domain of malc...@pointy-stick.com) client-ip=80.68.81.166;
Authentication-Results: mx.google.com; spf=neutral (google.com: 80.68.81.166 is neither permitted nor denied by best guess record for domain of malc...@pointy-stick.com) smtp.mail=malc...@pointy-stick.com
Received: from sharp.pointy-stick.com ([80.68.90.23])
by tallyho.bytemark.co.uk with esmtp (Exim 4.63)
(envelope-from <malc...@pointy-stick.com>)
id 1Jl0JC-0005Q0-NB
for django-users@googlegroups.com; Sun, 13 Apr 2008 11:23:42 +0000
Received: from [192.168.0.102] (cust7071.nsw01.dataco.com.au [203.171.88.159])
by sharp.pointy-stick.com (Postfix) with ESMTP id 90218C406
for <django-users@googlegroups.com>; Sun, 13 Apr 2008 21:23:40 +1000 (EST)
Subject: Feel free to test queryset-refactor branch
From: Malcolm Tredinnick <malc...@pointy-stick.com>
To: django-users@googlegroups.com
Content-Type: text/plain
Date: Sun, 13 Apr 2008 21:23:34 +1000
Message-Id: <1208085814.17060.31.camel@counterweight.tredinnick.org>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.3 (2.12.3-3.fc8)
Content-Transfer-Encoding: 7bit
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/
|
