On Sat, Apr 3, 2010 at 9:58 PM, Dennis Kaarsemaker
wrote:
> On ma, 2010-03-22 at 08:53 -0400, Karen Tracey wrote:
>> On Mon, Mar 22, 2010 at 4:07 AM, Raffaele Salmaso
>> wrote:
>> Marcob wrote:
>> > Please, does anybody know
On ma, 2010-03-22 at 08:53 -0400, Karen Tracey wrote:
> On Mon, Mar 22, 2010 at 4:07 AM, Raffaele Salmaso
> wrote:
> Marcob wrote:
> > Please, does anybody know which patch I need to apply to
> 1.1.1 to fix
> > this strange problem?
>
On Mon, Mar 22, 2010 at 4:07 AM, Raffaele Salmaso <
raffaele.salm...@gmail.com> wrote:
> Marcob wrote:
> > Please, does anybody know which patch I need to apply to 1.1.1 to fix
> > this strange problem?
> http://code.djangoproject.com/changeset/12807 ?
>
>
No, turns out it was a change made
Marcob wrote:
> Please, does anybody know which patch I need to apply to 1.1.1 to fix
> this strange problem?
http://code.djangoproject.com/changeset/12807 ?
--
()_() | That said, I didn't actually _test_ my patch. | +
(o.o) | That's what users are for! | +---+
It's about 4 hours I'm trying to find the real culprit...
To narrow the problem I create the simplest admin test:
from django.test import TestCase
class AdminViewBasicTest(TestCase):
def testAdmin(self):
from django.contrib.auth.models import User
user =