Hi,
On Thursday, December 20, 2012 9:29:06 PM UTC+1, Francisco Vieira wrote:
>
> Oh, and by the way, I'm using Django version 1.4.3. If this has already
> been fixed in 1.5 forget this...
>
I think I indeed fixed that for Django 1.5:
https://github.com/django/django/commit/367bfaa5226eaae32789
Hi. I've got a doubt about Django, but the reason I didn't post this on
django-users was because the doubt was about Django's behaviour/design.
If I was wrong to post here, I'm sorry.
The problem occured when I was defining a form class. I made changes in
a view, I wrote a form class and I made
Environment variable may be a better choice.
On Wed, Dec 19, 2012 at 3:41 PM, Steven Klass <
skl...@pivotalenergysolutions.com> wrote:
> Hi all,
>
> I know a number of us use PyCharm/Eclipse for Django development. As such
> the interpreters run `./manage.py runserver` directly from within the I
On Thursday 20 December 2012, Karen Tracey wrote:
> This has come up before, see: https://code.djangoproject.com/ticket/17974
>
Figures...
> 1.3 is security-fix only at this point,
Yes, and pretty close to not-even-security-fix; I'm well aware of that, and
that's why I wrote:
> > The issue fo
This has come up before, see: https://code.djangoproject.com/ticket/17974
1.3 is security-fix only at this point, we'd have to make a pretty big
exception to put anything into 1.3 to warn users of their mis-use of an
undocumented parameter to distinct
Karen
--
You received this message beca
Hi all,
We've encountered a funny bug in our code, which I thought was worth sharing.
I don't think a bug in Django is involved, but I suspect Django could do
better to prevent it.
The issue is with the distinct() method of querysets. Up to Django 1.3, it was
documented as taking no arguments;
