Conversation

Notices

1. eric casteleijn

   @sampattuzzi: the best analysis tool for #python code is the python interpreter, because of python's awesome introspection capabilities.

   Tuesday, 28-Jul-09 11:33:32 UTC from Gwibber
   • Jürgen Geuter

     @sampattuzzi: eric3 used to be able to generate diagrams from python code (if those help you)

     Tuesday, 28-Jul-09 10:54:14 UTC
   • Space Hobo Python

     @sampattuzzi what sort of !python analysis do you need? Most editors will color on syntax, and exuberant ctags can help trace definitions...

     Tuesday, 28-Jul-09 11:00:29 UTC
   • microft

     @sampattuzzi vim

     Tuesday, 28-Jul-09 11:03:04 UTC
   • streetcleaner Python

     @sampattuzzi http://identi.ca/user/23702 Maybe you want to take a look at Winpdb? http://winpdb.org/ !python

     Tuesday, 28-Jul-09 11:03:46 UTC
   • Jan Claeys Python

     @sampattuzzi: pydoc (included with !python) & http://pypi.python.org/pypi/pudb might be useful too

     Tuesday, 28-Jul-09 11:13:02 UTC
   • eric casteleijn

     @sampattuzzi: try importing it in ipython, and playing with it. Also, a well placed "import pdb; pdb.set_trace()" can be very illuminating..

     Tuesday, 28-Jul-09 11:32:41 UTC
   • Stuart Langridge

     @thisfred prepare yourself for the barrage of questions that we've put on hold with "that's a thisfred question" for the last week ;)

     Monday, 03-Aug-09 23:10:15 UTC