Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4548371 By: acidd_uk
Gents, First off, great job with pydev, I do a lot of python development at work and I find Eclipse/Pydev a lot nicer than just using vim ;-) Anyway, within each (most) of our package directories we have a test directory. This contains unit tests for the modules in the package and is non-deliverable code, from the point of view of our customers. As such, it's exempt from our internal coding standards though obviously it's still readable/maintainable. As such, the unit tests generate *masses* of pylint errors, warnings etc, which tend to swamp the genuine errors coming from the 'real' code. Is there any way to get pydev to run pylint selectively? Because of the way pydev invokes pylint for modules, it seems we cannot use the --ignore=XXX options to pydev itself. All we really need is to be able to say 'if the module to be linted is in a package called 'test' then don't lint it. Is there any way to do this currently, or is it planned? Thanks in advance, Tom Dalton ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=293649 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Pydev-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pydev-users
