← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/developers/HACKING.txt

  • Committer: Vincent Ladeuil
  • Date: 2007-11-04 15:29:17 UTC
  • mfrom: (2961 +trunk)
  • mto: (2961.1.1 trunk)
  • mto: This revision was merged to the branch mainline in revision 2962.
  • Revision ID: v.ladeuil+lp@free.fr-20071104152917-nrsumxpk3dikso2c
Merge bzr.dev

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/HACKING.txt
470
470
they're displayed or handled.
471
471
 
472
472
 
 
473
Testing warnings
 
474
----------------
 
475
 
 
476
The Python ``warnings`` module is used to indicate a non-fatal code
 
477
problem.  Code that's expected to raise a warning can be tested through
 
478
callCatchWarnings.
 
479
 
 
480
The test suite can be run with ``-Werror`` to check no unexpected errors
 
481
occur.
 
482
 
 
483
However, warnings should be used with discretion.  It's not an appropriate
 
484
way to give messages to the user, because the warning is normally shown
 
485
only once per source line that causes the problem.  You should also think
 
486
about whether the warning is serious enought that it should be visible to
 
487
users who may not be able to fix it.
 
488
 
 
489
 
473
490
Interface implementation testing and test scenarios
474
491
---------------------------------------------------
475
492