<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/pychecker/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/pychecker/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Fri, 25 Nov 2011 11:49:20 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/pychecker/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Suppressions on line/code/comment level</title><link>https://sourceforge.net/p/pychecker/feature-requests/32/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;In practice I don't manage to get all warnings quieted/confirmed adequately and comfortably via .pycheckrc and __pychecker__ .&lt;br /&gt;
A mechanism is necessary to suppress locally e.g. via special comments.&lt;/p&gt;
&lt;p&gt;See also patch #1623076&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kxroberto</dc:creator><pubDate>Fri, 25 Nov 2011 11:49:20 -0000</pubDate><guid>https://sourceforge.net5bee34406c78a326da2ad12dfc1fc44c1ca382d7</guid></item><item><title>Check for valid type in super calls</title><link>https://sourceforge.net/p/pychecker/feature-requests/31/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be nice if pychecker could check for the&lt;br /&gt;
correct type in super() calls.  I common error I make&lt;br /&gt;
when copy and pasting is this:&lt;/p&gt;
&lt;p&gt;class X(object):&lt;/p&gt;
&lt;p&gt;def __init__(self):&lt;br /&gt;
super(Y, self).__init__()&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thomas Heller</dc:creator><pubDate>Fri, 02 Dec 2005 09:56:16 -0000</pubDate><guid>https://sourceforge.net1ae81fb5b9843758bebcb49c0c54a121f7d30588</guid></item><item><title>Should warn about "%d %d %d" % (1, 2)</title><link>https://sourceforge.net/p/pychecker/feature-requests/30/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Passing the wrong number of args to string printf-style&lt;br /&gt;
formatting should be detected.  e.g. this code should&lt;br /&gt;
be caught be pychecker:&lt;/p&gt;
&lt;p&gt;def f():&lt;br /&gt;
"%d %d %d" % (1, 2)&lt;/p&gt;
&lt;p&gt;This is a frustrating bug that's all too easy to do.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Andrew Bennetts</dc:creator><pubDate>Wed, 31 Aug 2005 11:59:43 -0000</pubDate><guid>https://sourceforge.net3e68780d3a6900cee8149ea6f3fbc331617a83d4</guid></item><item><title>assert is a keyword, not a function</title><link>https://sourceforge.net/p/pychecker/feature-requests/29/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be nice if pychecker could warn when assert&lt;br /&gt;
is called with a tuple, ie. looking like a function call.&lt;/p&gt;
&lt;p&gt;assert(exp,"message")&lt;/p&gt;
&lt;p&gt;assert is particularly dangerous when used like this.&lt;br /&gt;
print will do something, assert will do nothing, ever.&lt;/p&gt;
&lt;p&gt;Warning on other statements could still be good though.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Toyotomi Hideyoshi</dc:creator><pubDate>Fri, 29 Jul 2005 00:47:54 -0000</pubDate><guid>https://sourceforge.netde85ad102da9808f9741d014888ab8b278fba2b8</guid></item><item><title>implicit literal string concatenation</title><link>https://sourceforge.net/p/pychecker/feature-requests/28/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I found a very annoying bug in some of my code due to&lt;br /&gt;
a missing comma in a list defined as follows:&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; [&lt;br /&gt;
... 'dir1/','dir2/'&lt;br /&gt;
... 'dir3/'&lt;br /&gt;
... ]&lt;br /&gt;
['dir1/', 'dir2/dir3/']&lt;/p&gt;
&lt;p&gt;Note the missing comma are 'dir2/'&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; 'foo/''bar'&lt;br /&gt;
'foo/bar'&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; 'foo''bar'&lt;br /&gt;
'foobar'&lt;/p&gt;
&lt;p&gt;It would be nice if pychecker detected one of these &lt;br /&gt;
cases.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Toyotomi Hideyoshi</dc:creator><pubDate>Sun, 17 Jul 2005 14:34:18 -0000</pubDate><guid>https://sourceforge.net44e5d96ccfa7b7a23910a2e3c0ed147641902c7d</guid></item><item><title>identifiers list by function/method</title><link>https://sourceforge.net/p/pychecker/feature-requests/27/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;one report pychecker could do is to list the identifiers that&lt;br /&gt;
appear on each method or function, may be sorted alfabetically,&lt;br /&gt;
so it's easier to detect typos, specially on assigments. e.g.:&lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;def main (*unused): &lt;br /&gt;
factor1= 73 &lt;br /&gt;
factor2= 736 &lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;resutl= factor1*factor2 &lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;print result&lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;the report should look like:&lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;main:&lt;br /&gt;
factor1&lt;br /&gt;
factor2 &lt;br /&gt;
result &lt;br /&gt;
resutl &lt;br /&gt;
unused&lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;it's easier to find out that resutl is the typo and not result, as it &lt;br /&gt;
is reported now by pychecker: &lt;/p&gt;
&lt;p&gt;pycheck.py:7: No global (result) found &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Marcos Dione</dc:creator><pubDate>Fri, 01 Apr 2005 14:22:46 -0000</pubDate><guid>https://sourceforge.net69f7a3a924018b47deae5f37dec388f967e3abdc</guid></item><item><title>warn on dict.has_key[value] </title><link>https://sourceforge.net/p/pychecker/feature-requests/26/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;At least for me, a pretty common typo is something&lt;br /&gt;
like:&lt;/p&gt;
&lt;p&gt;dict = {}&lt;br /&gt;
dict['blippy'] = 'baz'&lt;/p&gt;
&lt;p&gt;if dict.has_key['blippy']:&lt;br /&gt;
whatever&lt;/p&gt;
&lt;p&gt;aka, using [] for has_key instead of proper () &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Adrian Likins</dc:creator><pubDate>Thu, 27 Jan 2005 20:01:51 -0000</pubDate><guid>https://sourceforge.neta1e373ccf6b57576c84f3404ec2cc44ac70aa90e</guid></item><item><title>Warn about octal literals.</title><link>https://sourceforge.net/p/pychecker/feature-requests/25/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be useful if PyChecker warned you when you&lt;br /&gt;
specify an octal literal and where the value would&lt;br /&gt;
differ from what you might expect if you didn't&lt;br /&gt;
*realise* that you were specifying an octal literal.&lt;/p&gt;
&lt;p&gt;x = 04 # This doesn't need a warning: 04 == 4&lt;br /&gt;
#x = 09 # This doesn't need a warning: it will fail to&lt;br /&gt;
compile&lt;br /&gt;
x= 012 # This *does* need a warning: 012 == 10&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Simon Brunning</dc:creator><pubDate>Fri, 14 Jan 2005 12:02:23 -0000</pubDate><guid>https://sourceforge.net2d72cfa65802f8ef6b0b6f5496e61f5dcf8558cc</guid></item><item><title>Can pychecker be faster? - Whitelist?</title><link>https://sourceforge.net/p/pychecker/feature-requests/24/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi, I'm trying to integrate pychecker in pydev (python&lt;br /&gt;
plugin for eclipse), and I would like to know if there&lt;br /&gt;
is any way to check only a single file. &lt;/p&gt;
&lt;p&gt;It could be some sort of a white list or something like&lt;br /&gt;
that, as I would be analyzing the file automatically&lt;br /&gt;
each time the file is saved, and pychecker gets really&lt;br /&gt;
slow when I do that. Some files seem to take forever to&lt;br /&gt;
analyze... I have some files that can take up to 5&lt;br /&gt;
minutes to be analyzed, as they import many things...&lt;br /&gt;
(Having a black list is also not useful, especially&lt;br /&gt;
when it is analyzed only after the results are gotten...)&lt;/p&gt;
&lt;p&gt;Resuming, I would like to analyze everything in the&lt;br /&gt;
first time, after that, I would be working only with&lt;br /&gt;
deltas (so it could be much faster having a white list&lt;br /&gt;
so that only the delta is analyzed - normally only 1 or&lt;br /&gt;
2 files).&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Fabio Zadrozny</dc:creator><pubDate>Tue, 26 Oct 2004 10:36:18 -0000</pubDate><guid>https://sourceforge.net15a4cea1d5f2d1e70aaf3233231731d369b6f317</guid></item><item><title>Can pychecker be faster? - Whitelist?</title><link>https://sourceforge.net/p/pychecker/feature-requests/23/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi, I'm trying to integrate pychecker in pydev (python&lt;br /&gt;
plugin for eclipse), and I would like to know if there&lt;br /&gt;
is any way to check only a single file. &lt;/p&gt;
&lt;p&gt;It could be some sort of a white list or something like&lt;br /&gt;
that, as I would be analyzing the file automatically&lt;br /&gt;
each time the file is saved, and pychecker gets really&lt;br /&gt;
slow when I do that. Some files seem to take forever to&lt;br /&gt;
analyze... I have some files that can take up to 5&lt;br /&gt;
minutes to be analyzed, as they import many things...&lt;br /&gt;
(Having a black list is also not useful, especially&lt;br /&gt;
when it is analyzed only after the results are gotten...)&lt;/p&gt;
&lt;p&gt;Resuming, I would like to analyze everything in the&lt;br /&gt;
first time, after that, I would be working only with&lt;br /&gt;
deltas (so it could be much faster having a white list&lt;br /&gt;
so that only the delta is analyzed - normally only 1 or&lt;br /&gt;
2 files).&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Fabio Zadrozny</dc:creator><pubDate>Mon, 25 Oct 2004 13:08:14 -0000</pubDate><guid>https://sourceforge.nete1cd92c911e805c707804f65dd9b21b14fa862ca</guid></item></channel></rss>