Comments

• 2006/10/13

  added a test case but can't reproduce this. Test on windows ?
• 2006/10/13

  a similar pb :

  I found a minor problem in pylint. To reproduce this, create an empty
  directory, go into it and create a file named "__init__.py". The contents
  of the file can be something very simple, for example:
   print "hello world"
  
  Now if you run "pylint __init__.py", you will get the expected output.
  But if you run "pylint .", the output will look like this:
   ************* Module
   C:  0: Invalid name "" (should match
  (([a-z_][a-z0-9_]*)|([A-Z][a-zA-Z0-9]+))$)
   W:  0: Missing docstring
   W:  0: Missing required attribute "__revision__"
   C:  0: Invalid name "" (should match
  (([a-z_][a-z0-9_]*)|([A-Z][a-zA-Z0-9]+))$)
   W:  0: Missing docstring
   W:  0: Missing required attribute "__revision__"
  
  If you add some more lines (5 is enough), pylint will even report
  copy-pasted code between these "two" modules.
  
  So it seems pylint is checking "__init__.py" twice, once under its own
  name and once named empty string (probably the name of the containing
  module).
  
• 2008/05/13
  similar issue reported on pydev tracker : https://sourceforge.net/tracker/?func=detail&atid=577329&aid=1957009&group_id=85796