Gmail Calendar Documents Reader Web more »
Recently Visited Groups | Help | Sign in
Google Groups Home
Testing warnings
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Jeremy Dunck  
View profile  
 More options Nov 4, 8:19 pm
From: Jeremy Dunck <jdu...@gmail.com>
Date: Wed, 4 Nov 2009 17:19:08 -0800
Local: Wed, Nov 4 2009 8:19 pm
Subject: Testing warnings
I'm preparing a patch to make querysets call warnings.warn  
if .iterator is used multiple times on a single qs.

I don't see any examples of verification of warnings in the current  
test suite. Any suggestions on how best to test this?


    Reply    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Alex Gaynor  
View profile  
 More options Nov 4, 8:21 pm
From: Alex Gaynor <alex.gay...@gmail.com>
Date: Wed, 4 Nov 2009 20:21:31 -0500
Local: Wed, Nov 4 2009 8:21 pm
Subject: Re: Testing warnings

On Wed, Nov 4, 2009 at 8:19 PM, Jeremy Dunck <jdu...@gmail.com> wrote:

> I'm preparing a patch to make querysets call warnings.warn
> if .iterator is used multiple times on a single qs.

> I don't see any examples of verification of warnings in the current
> test suite. Any suggestions on how best to test this?

Warnings should just go to stdout (or perhaps stderr) in any event it
should be similar to picking up on a print statement wouldn't they?

Alex

--
"I disapprove of what you say, but I will defend to the death your
right to say it." -- Voltaire
"The people's good is the highest law." -- Cicero
"Code can always be simpler than you think, but never as simple as you
want" -- Me


    Reply    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2009 Google