On Thu, Feb 5, 2009 at 5:47 PM, Tai Lee wrote:
> I'd like to bring attention to several tickets that have been sitting
> unreviewed for 3-5 months.
I'm just about to head out, but if nobody else gets to these before
tomorrow morning I'll review 'em then.
Thanks!
Jacob
--~--~-~--~~
I'd like to bring attention to several tickets that have been sitting
unreviewed for 3-5 months. Most are fairly trivial fixes for bugs and
inconsistencies. Most have a patch and/or tests. I believe that all
are backwards compatible. I'd really appreciate feedback from any core
developers, or anot
On Thu, Feb 5, 2009 at 6:38 PM, Justin Bronn wrote:
>
> > Is there a way that default managers can be taken into
> > consideration when filtering through related fields? I don't know
> > exactly how this is supposed to work, is this the desired behavior?
> >
>
> It's not a bug, it's a feature :)
> Is there a way that default managers can be taken into
> consideration when filtering through related fields? I don't know
> exactly how this is supposed to work, is this the desired behavior?
>
It's not a bug, it's a feature :) Specifically, it's an artifact from
the 'fix' in #7666 -- fortuna
You're not asking it to filter on the current site. Shouldn't you use :
'User.objects.filter
(photos__name="photo_name").filter(photos__site__id=1)'
- Original Message -
From: django-developers@googlegroups.com
To: Django developers
Cc: evan.rei...@gmail.com
Sent: Thu Feb 05 17:21:11
On Thu, Feb 5, 2009 at 5:21 PM, Stephen Sundell
wrote:
>
> Say I have a model like this:
>
> class Photo(models.Model):
>name = models.CharField(max_length=25)
>user = models.ForeignKey(User,related_name='photos')
>image = models.ImageField()
>site = models.ForeignKey(Site,related_
Say I have a model like this:
class Photo(models.Model):
name = models.CharField(max_length=25)
user = models.ForeignKey(User,related_name='photos')
image = models.ImageField()
site = models.ForeignKey(Site,related_name='site_photos')
objects = CurrentSiteManager()
I've notic
On Thu, Feb 5, 2009 at 9:01 AM, Vinicius Mendes wrote:
> So I decided to write a new messages app and it works very well, the only
> problem is the django.core.context_processors.auth.
Yeah, this processor has a bunch of bugs in it. I think Malcolm and I
figured out that there's something like f
Hi guys, I didn't like the messages buit-in contrib/auth application. That's
becouse of two points:
- It don't give the ability to send messages to anonymous users (I saw that
it is one of the planned features for 1.1);
- There's no way to distinguish the messages. For example: I like my success
m
