For the record, here is the ticket:
https://code.djangoproject.com/ticket/16329
Best regards,
Cesar Canassa
2011/6/24 Russell Keith-Magee
> On Fri, Jun 24, 2011 at 2:08 PM, Cesar Canassa
> wrote:
> > I think I solved this! The reason why the test cases were taking so long
>
. When this happens in Django 1.2.3 it
initialize the both databases, but in Django 1.3 it doesn't initialize the
second. I just had to change the names and now the tests are running back in
the usual speed!
This was very hard to debbug, maybe Django should include a warning message
in cas
the Django 1.2.5 source to do more investigation.
Best regards,
Cesar Canassa
2011/6/21 Russell Keith-Magee
> On Wed, Jun 22, 2011 at 1:31 AM, Cesar Canassa
> wrote:
> > I am working in a large Django project that is currently using the 1.2.3
> > version. The project test
times longer than it did with the 1.2.3 version.
Has anyone had a similar issue? I have a felling that this related to
running Django under Windows.
Regards,
Cesar Canassa
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to t
ns and even admin integration! I suggest that you check it out.
Regards,
Cesar Canassa
2010/10/6 Paweł Roman
> Yuck, in_bulk() is useless! I thought it would return a nice
> dictionary just as expected, but instead it makes me deliver a list of
> keys first. Why?
>
> Eventua
I don't I will be able to keep a version control of the sprites and
rollback changes if required.
Any opinions?
Thanks,
Cesar Canassa
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django
6 matches
Mail list logo