Hi all,

On 12/28/05, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:

> Given that the (relatively) new Q() syntax for query construction
> doesn't require the top level kwarg, doesn't it make sense to allow
> unnamed *opts parameters as well as **kwargs in query functions?

Following the overwhelming response (accompanied by the sound of
crickets chirping in the distance :-), I've worked up a patch that
implements this change. It's logged as Ticket #1133.

Given that all the DB stuff is about to change, the patch is against
the magic-removal branch (which, by the way, is looking really good -
kudos to all concerned).

Yours,
Russ Magee

Reply via email to