explicit trailing whitespace, avoid temptation to drop those (thx Martin)

authorSylvain Th?nault <sylvain.thenault@logilab.fr>
changeset8f8420148961
branchdefault
phasepublic
hiddenno
parent revision#19502af3b7c9 Add --ignore-imports option to similarity checking. Closes #106534.
child revision#d05c55738d58 0.26
files modified by this revision
lint.py
# HG changeset patch
# User Sylvain Thénault <sylvain.thenault@logilab.fr>
# Date 1349430207 -7200
# Fri Oct 05 11:43:27 2012 +0200
# Node ID 8f8420148961b042c288a26892efd886d12078eb
# Parent 19502af3b7c9f321aafae7f1772ac2d6bca4b714
explicit trailing whitespace, avoid temptation to drop those (thx Martin)

diff --git a/lint.py b/lint.py
@@ -858,36 +858,36 @@
1          linter.load_default_plugins()
2          # load command line plugins
3          linter.load_plugin_modules(self._plugins)
4          # add some help section
5          linter.add_help_section('Environment variables', config.ENV_HELP, level=1)
6 -        linter.add_help_section('Output', '''
7 -Using the default text output, the message format is :                          
8 -                                                                                
9 -        MESSAGE_TYPE: LINE_NUM:[OBJECT:] MESSAGE                                
10 -                                                                                
11 -There are 5 kind of message types :                                             
12 -    * (C) convention, for programming standard violation                        
13 -    * (R) refactor, for bad code smell                                          
14 -    * (W) warning, for python specific problems                                 
15 -    * (E) error, for probable bugs in the code                                  
16 -    * (F) fatal, if an error occurred which prevented pylint from doing further
17 -processing.
18 -        ''', level=1)
19 -        linter.add_help_section('Output status code', '''
20 -Pylint should leave with following status code:                                 
21 -    * 0 if everything went fine                                                 
22 -    * 1 if a fatal message was issued                                           
23 -    * 2 if an error message was issued                                          
24 -    * 4 if a warning message was issued                                         
25 -    * 8 if a refactor message was issued                                        
26 -    * 16 if a convention message was issued                                     
27 -    * 32 on usage error                                                         
28 -                                                                                
29 -status 1 to 16 will be bit-ORed so you can know which different categories has
30 -been issued by analysing pylint output status code
31 -        ''', level=1)
32 +        linter.add_help_section('Output',
33 +'Using the default text output, the message format is :                          \n'
34 +'                                                                                \n'
35 +'        MESSAGE_TYPE: LINE_NUM:[OBJECT:] MESSAGE                                \n'
36 +'                                                                                \n'
37 +'There are 5 kind of message types :                                             \n'
38 +'    * (C) convention, for programming standard violation                        \n'
39 +'    * (R) refactor, for bad code smell                                          \n'
40 +'    * (W) warning, for python specific problems                                 \n'
41 +'    * (E) error, for probable bugs in the code                                  \n'
42 +'    * (F) fatal, if an error occurred which prevented pylint from doing further\n'
43 +'processing.\n'
44 +        , level=1)
45 +        linter.add_help_section('Output status code',
46 +'Pylint should leave with following status code:                                 \n'
47 +'    * 0 if everything went fine                                                 \n'
48 +'    * 1 if a fatal message was issued                                           \n'
49 +'    * 2 if an error message was issued                                          \n'
50 +'    * 4 if a warning message was issued                                         \n'
51 +'    * 8 if a refactor message was issued                                        \n'
52 +'    * 16 if a convention message was issued                                     \n'
53 +'    * 32 on usage error                                                         \n'
54 +'                                                                                \n'
55 +'status 1 to 16 will be bit-ORed so you can know which different categories has\n'
56 +'been issued by analysing pylint output status code\n',
57 +        level=1)
58          # read configuration
59          linter.disable('W0704')
60          linter.read_config_file()
61          # is there some additional plugins in the file configuration, in
62          config_parser = linter.cfgfile_parser