Maybe a quick mention in the docs saying: "Warning, this might not work in such and such case. But it is worked on and should be eventually fixed, see the queryset-refactor branch."
I have to say that I spent quite some time trying to find out what was wrong with my code, as I fully trusted the docs (and so should we). A quick mention like that would have saved me quite some time and frustration ;) On Feb 13, 9:13 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Wed, 2008-02-13 at 00:27 -0800, [EMAIL PROTECTED] wrote: > > Perhaps the current documentation should be updated to reflect that > > this is not working. Its quite frustrating to have documentation that > > describes something as working when it is not. > > > On Feb 12, 1:20 am, Malcolm Tredinnick <[EMAIL PROTECTED]> > > wrote: > > > On Tue, 2008-02-12 at 00:56 -0800, Julien wrote: > > > > Thanks a lot for the tips! I think I'll go for the custom merging in > > > > Python. > > > > > One stupid question. Is there any estimation as to when queryset- > > > > refactor might be merged to trunk? I know it's hard to answer, but > > > > should it be more like 1 month, 6 month, 1 year away? :) > > > > The wiki says it's pretty unstable, so I guess it won't happen before > > > > a while... > > > > Hopefully pretty soon. We're in the home stretch now and soon I'll be > > > asking for volunteers to test it. > > Since the majority of OR lookups work, this isn't worth doing. It's a > better use of our time to fix the problems. > > Regards, > Malcolm > > -- > Honk if you love peace and quiet.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 -~----------~----~----~----~------~----~------~--~---
