On Tue Nov 25 2014 at 2:27:46 PM Dave Halter
wrote:
> 2014-11-25 12:29 GMT+01:00 Stefan Bucur :
>
>>
>>
>> On Tue Nov 18 2014 at 2:01:46 PM Dave Halter
>> wrote:
>>
>>> Hi Stefan
>>>
>>> I'm playing with this as well in Jedi. I'm pretty far with flow analysis
>>> and AttributeErrors. (This inclu
2014-11-25 12:29 GMT+01:00 Stefan Bucur :
>
>
> On Tue Nov 18 2014 at 2:01:46 PM Dave Halter
> wrote:
>
>> Hi Stefan
>>
>> I'm playing with this as well in Jedi. I'm pretty far with flow analysis
>> and AttributeErrors. (This includes everything you mention above except
>> integer division by zer
On Tue Nov 18 2014 at 2:01:46 PM Dave Halter
wrote:
> Hi Stefan
>
> I'm playing with this as well in Jedi. I'm pretty far with flow analysis
> and AttributeErrors. (This includes everything you mention above except
> integer division by zero). Would be easy to implement in Jedi, though. I
> just
On Tue Nov 18 2014 at 1:25:07 PM Claudiu Popa wrote:
> On Mon, Nov 17, 2014 at 7:18 PM, Stefan Bucur
> wrote:
> > I'm developing a Python static analysis tool that flags common
> programming
> > errors in Python programs. The tool is meant to complement other tools
> like
> > Pylint (which perfo
On Mon, Nov 17, 2014 at 05:18:03PM +, Stefan Bucur wrote:
> I wanted first to tap into people's experience and get a sense of what
> common pitfalls in the language & its standard library such a static
> checker should look for.
[...]
> * Proper Unicode handling (for 2.x)
> - encode() is not
Hi Stefan
I'm playing with this as well in Jedi. I'm pretty far with flow analysis
and AttributeErrors. (This includes everything you mention above except
integer division by zero). Would be easy to implement in Jedi, though. I
just have different priorities, at the moment.
If you have some time
On Mon, Nov 17, 2014 at 7:18 PM, Stefan Bucur wrote:
> I'm developing a Python static analysis tool that flags common programming
> errors in Python programs. The tool is meant to complement other tools like
> Pylint (which perform checks at lexical and AST level) by going deeper with
> the code a
Stefan Bucur
writes:
> For instance, a path-sensitive analysis detects that the following
> snippet of code would raise an AttributeError exception:
>
> if object is None: # If the True branch is taken, we know the object is None
> object.doSomething() # ... so this statement would always fail
I'm developing a Python static analysis tool that flags common programming
errors in Python programs. The tool is meant to complement other tools like
Pylint (which perform checks at lexical and AST level) by going deeper with
the code analysis and keeping track of the possible control flow paths i
