On Sep 14, 2013 11:00 AM, "Balachandran Sivakumar"
wrote:
> When you find some time, please do post a few Python
> dtrace one-liners here. It would be useful to the rest of us. Thanks
Oh... man... I want to +1 this... so... many... times!!!
Ram, you should totally share your experiences with thi
Hi Sriram,
On Sat, Sep 14, 2013 at 6:35 AM, Sriram Narayanan wrote:
>
> I've resumed learning dtrace for debugging on production. Given Paul Fox'
> work on dtrace for Linux (apart from dtrace being production ready on bsd
> and Solaris), and the dtrace patches for Python ( both of which I haven't
On Sep 14, 2013 6:37 AM, "Sriram Narayanan" wrote:
> [...]
> I think using dtrace will be most effective going forward.
Hear, hear! DTrace FTW!!
- d
___
BangPypers mailing list
BangPypers@python.org
https://mail.python.org/mailman/listinfo/bangpypers
On Sep 13, 2013 3:58 PM, "Saager Mhatre" wrote:
>
> On Fri, Sep 13, 2013 at 2:46 PM, Anand Chitipothu wrote:
>
> > On Fri, Sep 13, 2013 at 2:36 PM, Dhruv Baldawa > >wrote:
> >
> > > This is what I use for debugging:
> > > from IPython.core.debugger import Tracer; Tracer()()
> > >
> > > works most
PDBTrack - http://www.emacswiki.org/emacs/PdbTrack
--
Cordially,
Noufal
http://nibrahim.net.in
___
BangPypers mailing list
BangPypers@python.org
https://mail.python.org/mailman/listinfo/bangpypers
On Fri, Sep 13, 2013 at 2:46 PM, Anand Chitipothu wrote:
> On Fri, Sep 13, 2013 at 2:36 PM, Dhruv Baldawa >wrote:
>
> > This is what I use for debugging:
> > from IPython.core.debugger import Tracer; Tracer()()
> >
> > works mostly like pdb, with some nice features like tab completions
> >
>
> Th
I use traceback with exception(dummy exception) to find the flow of the
programme (files, methods, statements, etc--)
import traceback
traceback.print_exc()
Regards
Saju Madhavan
+91 09535134654
On Fri, Sep 13, 2013 at 3:18 PM, Bibhas wrote:
> Yeah. Pudb is good. But I could not leave the simp
Yeah. Pudb is good. But I could not leave the simplistic debugging with print
and pdb.
Guruprasad wrote:
>On Fri, Sep 13, 2013 at 2:51 PM, Kushal Das
>wrote:
>> On Fri, Sep 13, 2013 at 2:46 PM, Anand Chitipothu
> wrote:
>>
>>> The best debugging tool I've used so far is the print statement.
>W
On Fri, Sep 13, 2013 at 2:51 PM, Kushal Das wrote:
> On Fri, Sep 13, 2013 at 2:46 PM, Anand Chitipothu
> wrote:
>
>> The best debugging tool I've used so far is the print statement. What about
>> others?
> Works for me in 99% of time or else there is ipdb.
I heard about pudb (https://pypi.pytho
My choice is winpdb. It is great to debug multi threaded applications.
Regards,
Harish
On Fri, Sep 13, 2013 at 2:46 PM, Anand Chitipothu wrote:
> On Fri, Sep 13, 2013 at 2:36 PM, Dhruv Baldawa >wrote:
>
> > This is what I use for debugging:
> > from IPython.core.debugger import Tracer; Tracer(
On Fri, Sep 13, 2013 at 2:46 PM, Anand Chitipothu wrote:
> The best debugging tool I've used so far is the print statement. What about
> others?
Works for me in 99% of time or else there is ipdb.
Kushal
--
http://fedoraproject.org
http://kushaldas.in
On Fri, Sep 13, 2013 at 2:36 PM, Dhruv Baldawa wrote:
> This is what I use for debugging:
> from IPython.core.debugger import Tracer; Tracer()()
>
> works mostly like pdb, with some nice features like tab completions
>
The best debugging tool I've used so far is the print statement. What about
ot
This is what I use for debugging:
from IPython.core.debugger import Tracer; Tracer()()
works mostly like pdb, with some nice features like tab completions
--
Dhruv Baldawa
(http://www.dhruvb.com)
On Fri, Sep 13, 2013 at 1:34 PM, Saju M wrote:
> Hi,
>
> What are the functions/tools/ways you gu
Hi,
What are the functions/tools/ways you guys are using for debugging.
Like,,
To get list of attributes of a module, class, instance, ---
---
dir(object)
To get __dict__ attribute of a module, class, instance, ---
---
vars(object)
Debugger
import pdb; pdb.set_tr
14 matches
Mail list logo
