Hi!
I think that making contents of proposed extensions subdirectory a separate
package from pylint itself would be a great convenience for users who may
not be ready to update to most recent version of pylint, but are interested
in some optional checker.
Please let me know what you think.
Thank
On Dec 4, 2014 3:19 PM, "Anne Mulhern" wrote:
>
> Hi!
>
> I think that making contents of proposed extensions subdirectory a
separate
> package from pylint itself would be a great convenience for users who may
> not be ready to update to most recent version of pylint, but are
interested
> in some
Thanks!
I ended up getting less ambitious with the analysis,
but the definition of close() method in Misdesign checker
seemed like a good working example to start with.
- mulhern
- Original Message -
> From: "Torsten Marek"
> To: "Anne Mulhern"
> Cc: "code-quality"
> Sent: Friday, Nov
Hi!
Would it be possible to be able to extend pylint somehow to
record a time cost for individual pylint analyses?
- mulhern
___
code-quality mailing list
[email protected]
https://mail.python.org/mailman/listinfo/code-quality