To complement the above list of locations where
Site.objects.get_current is still in use, I have generated the
following list of locations in the code where settings.SITE_ID
continues to be in use:
$ grep -nr SITE_ID * | grep -v svn | grep -v pyc
conf/project_template/settings.py:39:SITE_ID = 1
co
See the wiki page for more details and to sign up:
http://code.djangoproject.com/wiki/Sprint2011JanAustin
Gary
--
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 uns
On Wed, Jan 19, 2011 at 10:29:25AM +0800, Russell Keith-Magee wrote:
> On Wed, Jan 19, 2011 at 10:07 AM, wrote:
> >
> > In that case, I would assume the test case in that bug submission is
> > sufficient
> > for the purpose at hand.
>
> Yes, the test case is sufficient.
>
> > If there's anythi
On Wed, Jan 19, 2011 at 10:07 AM, wrote:
>
> In that case, I would assume the test case in that bug submission is
> sufficient
> for the purpose at hand.
Yes, the test case is sufficient.
> If there's anything else I can do, let me know.
Well... you could fix the bug :-)
Russ %-)
--
You re
On Wed, Jan 19, 2011 at 09:26:39AM +0800, Russell Keith-Magee wrote:
> On Wed, Jan 19, 2011 at 5:50 AM, wrote:
> > On Tue, Jan 18, 2011 at 10:23:33PM +0100, ??ukasz Rekucki wrote:
> >> On 18 January 2011 20:07, ? wrote:
> >> > #14930 was closed wontfix blaming a buggy version of Python (2.6.1) fo
On Wed, Jan 19, 2011 at 5:50 AM, wrote:
> On Tue, Jan 18, 2011 at 10:23:33PM +0100, ??ukasz Rekucki wrote:
>> On 18 January 2011 20:07, wrote:
>> > #14930 was closed wontfix blaming a buggy version of Python (2.6.1) for the
>> > issue. ??I've reproduced the same issue on Python 2.6.6 and on 2.7
On Tue, Jan 18, 2011 at 10:23:33PM +0100, ??ukasz Rekucki wrote:
> On 18 January 2011 20:07, wrote:
> > #14930 was closed wontfix blaming a buggy version of Python (2.6.1) for the
> > issue. ??I've reproduced the same issue on Python 2.6.6 and on 2.7.1.
> > ??I've only
> > reproduced the issue o
On 18 January 2011 20:07, wrote:
> #14930 was closed wontfix blaming a buggy version of Python (2.6.1) for the
> issue. I've reproduced the same issue on Python 2.6.6 and on 2.7.1. I've
> only
> reproduced the issue on Django 1.2.3, however.
What issue did you actually reproduce ? The expecte
#14930 was closed wontfix blaming a buggy version of Python (2.6.1) for the
issue. I've reproduced the same issue on Python 2.6.6 and on 2.7.1. I've only
reproduced the issue on Django 1.2.3, however.
In other words, it's looking more and more (to me, anyway) as if this bug is a
legitimate Djang
