On 9/4/06, Ned Batchelder <[EMAIL PROTECTED]
> wrote:
I've been experimenting with the new test frameworks, and am veryexcited about their potential.I've hit a snag, and am wondering if it reveals a flaw in the currentmanagement.py, or if there is something I don't understand yet (most
likely the l
On 9/4/06, Matthew Flanagan <[EMAIL PROTECTED]> wrote:
and use ./manage.py --settings=myapp.testsettings.I briefly considered this approach when the TEST_DATABASE_NAME suggestion came up. However, I was concered about the possibility for accidentally nuking your production database. If you ever for
Jacob Kaplan-Moss wrote:
> On Aug 25, 2006, at 7:04 AM, DavidA wrote:
> > One comment on ValidationErrors: When I've done these types of things
> > in the past, I've typically returned two levels of validations
> > messages: warnings and errors. An error indicates that the attempted
> > save will
Russell Keith-Magee wrote:
> On 9/4/06, Ned Batchelder <[EMAIL PROTECTED]> wrote:
>> Partly on this topic: I would very much like to use sqlite in-memory
>> databases for testing, even though I use MySQL for deployment. The speed
>> difference is 10x. One way to do this is to have a TEST_DATAB
Hi.
I have 'issues' with Contexts, RequestContexts and templatetags.
Possibly this is my problem and not Django's, but I'd like to be
persuaded of that.
I want to get the user in a templatetag, which seems like a perfectly
reasonable and common thing to want to do. As far as I can tell the way
t
I've been experimenting with the new test frameworks, and am very
excited about their potential.
I've hit a snag, and am wondering if it reveals a flaw in the current
management.py, or if there is something I don't understand yet (most
likely the latter). Russ's test runner uses management.sy
Matthew Flanagan wrote:
On 04/09/06, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
On 9/4/06, Ned Batchelder <[EMAIL PROTECTED]> wrote:
Partly on this topic: I would very much like to use sqlite in-memory
databases for testing, even though I use
Hello all.
Since Django apps tend to function in multi-process environments (both
in mod_python and FastCGI modes), I've faced a necessity to route
events between processes that execute Django application instances.
Django uses PyDispatcher to dispatch events, but it's a single-process
and can not
On 9/4/06, SmileyChris <[EMAIL PROTECTED]> wrote:
I can't see that you've missed anything (but then again, I didn'tmanage to get it right on my attempt so don't trust me) ;)I've just committed the fix (along with some extra unit tests to make sure it stays fixed) as r3714. Thanks for the help in na
