This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author typo.pl
Recipients amaury.forgeotdarc, loewis, mark.dickinson, pitrou, typo.pl
Date 2008-12-19.06:34:21
SpamBayes Score 1.9296289e-07
Marked as misclassified No
Message-id <1229668463.92.0.119904086431.issue4653@psf.upfronthosting.co.za>
In-reply-to
Content
> It's difficult to really test such errors.

When I can't control the called function, I usually step through the 
code in a debugger and change the result variable in question to the 
appropriate value to see if the code handles failed function calls 
correctly. 

In the three Win32 API cases, it's clear that the failure path was not 
tested.

And I can't see how the ferr if statement was tested with a failure 
value either.
History
Date User Action Args
2008-12-19 06:34:24typo.plsetrecipients: + typo.pl, loewis, amaury.forgeotdarc, mark.dickinson, pitrou
2008-12-19 06:34:23typo.plsetmessageid: <1229668463.92.0.119904086431.issue4653@psf.upfronthosting.co.za>
2008-12-19 06:34:22typo.pllinkissue4653 messages
2008-12-19 06:34:21typo.plcreate