On Tue, Jan 15, 2013 at 8:37 AM, Chris Kaynor wrote:
> And those aren't even covering the case that a, normally non-mutating,
> method actually mutates.
If it's static analysis, I'd quietly ignore those sorts of cases.
Anything can be changed any time, including stuff that's completely
unrelated
On 1/14/2013 4:28 PM, Chris Angelico wrote:
On Tue, Jan 15, 2013 at 6:48 AM, wrote:
I'd like to develop a small debugging tool for python programs.In Dynamic
Slicing How can I find the variables that are accessed in a statement? And find
the type of access (read or write) for those variables
On Mon, Jan 14, 2013 at 1:28 PM, Chris Angelico wrote:
> On Tue, Jan 15, 2013 at 6:48 AM, wrote:
> > I'd like to develop a small debugging tool for python programs.In
> Dynamic Slicing How can I find the variables that are accessed in a
> statement? And find the type of access (read or write) f
On Tue, Jan 15, 2013 at 6:48 AM, wrote:
> I'd like to develop a small debugging tool for python programs.In Dynamic
> Slicing How can I find the variables that are accessed in a statement? And
> find the type of access (read or write) for those variables (in Python).
> ### Write: A statement ca
I'd like to develop a small debugging tool for python programs.In Dynamic
Slicing How can I find the variables that are accessed in a statement? And find
the type of access (read or write) for those variables (in Python).
### Write: A statement can change the program state.
### Read : A statement
