[Python-projects] pylint bug (unreachable code)

[Arthur Lutz]

On Tue, Mar 03, 2009 at 12:16:04AM +0100, Vincent Legoll wrote:
> Hello,
> 
> I searched a bug tracker for pylint, but cannot find anything
> relevant on your website... That would be cool to search for
> already reported bugs before asking to the ML...

The bugtracker can be found on the project page : 

http://www.logilab.org/project/pylint 

Clic on the "tracker" tab to see all tickets related to pylint. 

For the rest of your question I'll let someone that know pylint better
than I do answer that. 

Arthur

ps. I've added that URL to the README file (it has mysteriously 
disappeared from it).
 
> So, here is my question:
> 
> In the following code:
> 
> ======================
> def a():
>         try:
>                 return
>         except:
>                 return
> 
>         raise Exception('a')
> ======================
> 
> Pylint does not report unreachable code, whereas
> if we remove the try / except from around the return,
> it does...
> 
> Is this an already known deficiency ?
> Is this not detectable ?
> 
> Thanks.
> 
> P.S. I'm using pylint to find defects in the meld diff viewer
> source code, and it's working great !
> 
> -- 
> Vincent Legoll
> _______________________________________________
> Python-Projects mailing list
> Python-Projects at lists.logilab.org
> http://lists.logilab.org/mailman/listinfo/python-projects

-- 
Arthur LUTZ                                    LOGILAB, Paris (France)
http://www.logilab.com   http://www.logilab.fr  http://www.logilab.org
Développement logiciel avancé - Intelligence Artificielle - Formations