ManyToManyField looks broken

2006-06-25 Thread Ivan Sagalaev
I'd like to draw some attention to ticket http://code.djangoproject.com/ticket/2232 (mainly russelm's attention as it appeared after his checkin 3195). Basically ManyToMany relations don't work when you try to get related queryset from a model where ManyToManyField is defined. Or is it just

Re: ManyToManyField looks broken

2006-06-25 Thread Malcolm Tredinnick
On Sun, 2006-06-25 at 14:04 +0400, Ivan Sagalaev wrote: > I'd like to draw some attention to ticket > http://code.djangoproject.com/ticket/2232 (mainly russelm's attention as > it appeared after his checkin 3195). > > Basically ManyToMany relations don't work when you try to get related > qu

Re: ManyToManyField looks broken

2006-06-25 Thread Malcolm Tredinnick
On Sun, 2006-06-25 at 20:20 +1000, Malcolm Tredinnick wrote: > On Sun, 2006-06-25 at 14:04 +0400, Ivan Sagalaev wrote: > > I'd like to draw some attention to ticket > > http://code.djangoproject.com/ticket/2232 (mainly russelm's attention as > > it appeared after his checkin 3195). > > > > Ba

Re: ManyToManyField looks broken

2006-06-25 Thread Ivan Sagalaev
Malcolm Tredinnick wrote: > Pretty much "just you", but it's obviously a little trickier than that. > This is basically ticket #1796 occurring again. I've dug a bit further and have found out that mentioned changeset (3195) has broken only certain relations (for cross-app models and another cas

Re: Error when iexact meets integer field.

2006-06-25 Thread favo
Thanks for helping :-) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to

Re: ManyToManyField looks broken

2006-06-25 Thread Russell Keith-Magee
On 6/25/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > > I'd like to draw some attention to ticket > http://code.djangoproject.com/ticket/2232 (mainly russelm's attention as > it appeared after his checkin 3195). Paying attention now :-) > Basically ManyToMany relations don't work when you try

Re: ManyToManyField looks broken

2006-06-25 Thread Malcolm Tredinnick
On Sun, 2006-06-25 at 22:39 +0800, Russell Keith-Magee wrote: > On 6/25/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > > > > I'd like to draw some attention to ticket > > http://code.djangoproject.com/ticket/2232 (mainly russelm's attention as > > it appeared after his checkin 3195). > > Paying

Re: RFC: Django history tracking

2006-06-25 Thread william
Uros Trebec wrote: > > Sounds nice, this is a feature I'm currently looking for... but I've > > already started my own implementation. > > Nice! Do you have anyting in code yet? Any bottlenecks? > sorry not yet. But will come, I need it for my current development. > > > I would just share it wit

TEMPLATE_STRING_IF_INVALID bug

2006-06-25 Thread Vladimir Pouzanov
Hello all, I've found something that looks like a bug. When I add TEMPLATE_STRING_IF_INVALID = 'INVALID' to my config, first page of admin (i.e. http://127.0.0.1:8000/admin/) is rendered without 'Django administration' headline. -- Sincerely, Vladimir "Farcaller" Pouzanov http://www.hackndev.co

Re: ManyToManyField looks broken

2006-06-25 Thread Ivan Sagalaev
Malcolm Tredinnick wrote: > I've just checked in r3202 which I believe fixes the root cause of #1796 > in a reasonably correct way. I think it also fixes #2232 for the same > reason. It does (just checked). Marking ticket fixed... Thank you very much, Malcolm and Russel and everyone else! --~--

Re: ManyToManyField looks broken

2006-06-25 Thread Martina Oefelein
Hi Russel, > 2) I have seen the behaviour from r1796 before - for me, the problem > ultimately turned out to be caused by a PYTHONPATH that included the > application directory (so "from myapp.models import Foo" and "from > myproject.myapp.models import Foo" were both legal). At the time, I > cha

Re: ManyToManyField looks broken

2006-06-25 Thread gabor
Malcolm Tredinnick wrote: > > I can no longer cause #1796 or anything like it to fail -- and I had a > couple of failing examples there. I believe relative imports > (appname.models, etc) might now work reliably too (experiments suggest > they do), which means you no longer are reliant on your pr

Re: ManyToManyField looks broken

2006-06-25 Thread Malcolm Tredinnick
On Mon, 2006-06-26 at 00:58 +1000, Malcolm Tredinnick wrote: > I've just checked in r3202 which I believe fixes the root cause of #1796 > in a reasonably correct way. I think it also fixes #2232 for the same > reason. It all seems to come down to the import paths being used as > dictionary keys a

Re: ManyToManyField looks broken

2006-06-25 Thread Malcolm Tredinnick
On Sun, 2006-06-25 at 18:36 +0200, gabor wrote: > Malcolm Tredinnick wrote: > > > > I can no longer cause #1796 or anything like it to fail -- and I had a > > couple of failing examples there. I believe relative imports > > (appname.models, etc) might now work reliably too (experiments suggest >

Re: ManyToManyField looks broken

2006-06-25 Thread Russell Keith-Magee
On 6/25/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > Russ: can you see if I've overlooked any problem there, please. It took > a little while to track everything down and my brain may have gotten > twisted in the process. The anti-model-duplication logic makes sense to me from what I und

Re: TEMPLATE_STRING_IF_INVALID bug

2006-06-25 Thread Russell Keith-Magee
On 6/25/06, Vladimir Pouzanov <[EMAIL PROTECTED]> wrote: > > I've found something that looks like a bug. I just tried and got the same thing. I've opened ticket #2237 to follow the problem, and added you to the CC list for that ticket. Thanks for the report, Russ Magee %-) --~--~-~--~--