What do people use for code analysis.

[Steven W. Orr]

Lots of code, calls to, calls by, inheritance, multiple tasks, etc.

What do people use to figure out what's happening?

TIA

--
Time flies like the wind. Fruit flies like a banana. Stranger things have .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net

[Laurent Pointal]

Steven W. Orr a écrit :

Lots of code, calls to, calls by, inheritance, multiple tasks, etc.

What do people use to figure out what's happening?

TIA

I've collected some links over time:

http://www.limsi.fr/Individu/pointal...liens-metaprog

You may look at
# depgraph - graphe de dépendances entre modules
# coverage - a Python module that measures code coverage during Python
execution
# pycover - a python coverage tool
# pycount - métrique de lignes sources Python
# depgraph - generating python module dependency graphs
# pycallgraph - génération du graphe d'appels pour les programmes Python
(nécessite GraphViz).