From austin at sixty-north.com  Wed Feb 24 04:26:02 2016
From: austin at sixty-north.com (Austin Bingham)
Date: Wed, 24 Feb 2016 10:26:02 +0100
Subject: [code-quality] Reusing the "message control" facilities in pylint,
 et al.
Message-ID: <CAM4P0NQe2EcYhW3cRpEvocoob+tftW_kEWp-QgTBw2B=ZD52MQ@mail.gmail.com>

Hi all,

I'm working on a mutation testing tool for Python, and one of the issues
I'll eventually have to sort out is how to let users disable certain
mutations in certain bits of code. One of the obvious approaches for this
is to use comments like pylint, so I'm interested in seeing if it's
possible to reuse the facilities that pylint has for this.

My needs are, I think, fairly similar: for specified blocks of code,
prevent (or perhaps otherwise modify) the application of certain mutation
operators. This feels much like telling pylint to ignore certain rules in
certain contexts.

So, at a high level, is this feature something that can be easily
repurposed? Is it designed for reuse? I'm not currently using astroid, just
the standard ast module, but I'm willing to switch to astroid if necessary.

Austin Bingham
Technical Director
Sixty North AS
austin at sixty-north.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/code-quality/attachments/20160224/d7472b8b/attachment.html>

From esr at thyrsus.com  Mon Feb 29 06:35:27 2016
From: esr at thyrsus.com (esr at thyrsus.com)
Date: Mon, 29 Feb 2016 06:35:27 -0500 (EST)
Subject: [code-quality] Problems in pylint.1
Message-ID: <20160229113527.82DFB13A1095@snark.thyrsus.com>

This is automatically generated email about markup problems in a man
page for which you appear to be responsible.  If you are not the right
person or list, please tell me so I can correct my database.

See http://catb.org/~esr/doclifter/bugs.html for details on how and
why these patches were generated.  Feel free to email me with any
questions.  Note: These patches do not change the modification date of
any manual page.  You may wish to do that by hand.

I apologize if this message seems spammy or impersonal. The volume of
markup bugs I am tracking is over five hundred - there is no real
alternative to generating bugmail from a database and template.

--
                             Eric S. Raymond
-------------- next part --------------
Problems with pylint.1:

Ambiguous or invalid backslash.  This doesn't cause groff a problem.
but it confuses doclifter and may confuse older troff implementations.

--- pylint.1-unpatched	2016-02-29 05:36:22.596489040 -0500
+++ pylint.1	2016-02-29 05:37:06.100375947 -0500
@@ -121,7 +121,7 @@
 .IP "--max-line-length=<int>"
 Maximum number of characters on a single line. [current: 80]
 .IP "--ignore-long-lines=<regexp>"
-Regexp for a line that is allowed to be longer than the limit. [current: ^\s*(# )?<?https?://\S+>?$]
+Regexp for a line that is allowed to be longer than the limit. [current: ^\es*(# )?<?https?://\eS+>?$]
 .IP "--single-line-if-stmt=<y_or_n>"
 Allow the body of an if to be on the same line as the test if there is no else. [current: no]
 .IP "--no-space-check=NO_SPACE_CHECK"