Dear django-developers,
It seems that Django has now become the argument for NOT fixing this
issue properly. Citing python-dev:
> For example, in the Django test
> suite, the HTML output is different at each run. Web browsers may
> render the web page differently, or crash, or ... I don't think t
So a few things we've done to take our test suite from 45 minutes to
12:
1. Implement global fixtures
These get loaded after syncing just like initial data. Obviously this
is a massive speed up
as you only reload them in between transaction test cases.
2. Don't inherit from TestCase if you aren'
On Thu, Jan 19, 2012 at 12:15 PM, Carl Meyer wrote:
> I don't think Adrian is proposing anything as extensive as #17. What
> he's proposing (IIUC) wouldn't change the semantics of your sample code
> at all. All it would do is prepopulate the FK field on the results of a
> reverse-FK query, so the
Hi again,
>
> john = Author.objects.get(name='john')
> books = list(john.book_set.all())
>
> # Does a database query, but should be smart enough to simply return john.
> books[0].author
> """
>
> I'm pretty sure there's a long-standing ticket for this, but I'm not
> sure which one it is. Shai,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/19/2012 11:02 AM, Jeremy Dunck wrote:
> On Thu, Jan 19, 2012 at 5:14 PM, Adrian Holovaty wrote:
>> john = Author.objects.get(name='john')
>> books = list(john.book_set.all())
>>
>> # Does a database query, but should be smart enough to simply re
On Thu, Jan 19, 2012 at 5:14 PM, Adrian Holovaty wrote:
> On Wed, Jan 18, 2012 at 1:07 PM, Shai Berger wrote:
>> I have a small improvement to suggest for one-to-one fields: Make them cache
>> back-references on related objects. That is, assume
>
> Yes! Good improvement. And we should do the same
On Mon, Jan 16, 2012 at 10:46 AM, Anssi Kääriäinen
wrote:
> I have been investigating what takes time in Django's test runner and
> if there is anything to do about it. The short answer is: yes, there
> is a lot of room for improvement. I managed to reduce the running
> speed of the test suite (on
On Wed, Jan 18, 2012 at 1:07 PM, Shai Berger wrote:
> I have a small improvement to suggest for one-to-one fields: Make them cache
> back-references on related objects. That is, assume
Yes! Good improvement. And we should do the same thing for one-to-many
fields (ForeignKeys):
"""
class Author(m
+1,
I think they ought to be auto imported just like models.py, views.py, etc. are.
From: Emil Stenström
Sent: Thursday, January 19, 2012 8:44 AM
To: django-developers@googlegroups.com
Subject: Re: Thoughts on defining and autoimporting signals.py
On Thursday, 22 December 2011 03:49:44 UTC+1
On Thursday, 22 December 2011 03:49:44 UTC+1, Russell Keith-Magee wrote:
> ... there isn't a single solution that will work
> everywhere, which one of the reasons that the docs are silent on the
> issue.
>
Just for the record: The docs are actually telling you to put your signals
in models.py, a
Hi,
On Wednesday, January 18, 2012 8:07:26 PM UTC+1, Shai Berger wrote:
>
> Do you see a reason why I should not post a ticket?
>
No, please go ahead. Funny you mention that problem now, I ran over the
same thing yesterday :)
Cheers,
Florian
--
You received this message because you are subscr
11 matches
Mail list logo