Alan G wrote:
>>>I think this approach to debugging won't scale well and you are
>
> just
>
>>>seeing the tip of the iceberg [and more helpful stuff,
>
> snipped.]
>
>>Thanks to you both. I think I may need to step up my "development
>>environment" beyond emacs and a command line.
>
>
>
> > I think this approach to debugging won't scale well and you are
just
> > seeing the tip of the iceberg [and more helpful stuff,
snipped.]
>
> Thanks to you both. I think I may need to step up my "development
> environment" beyond emacs and a command line.
I don't see why. The very biggest
On Thu, 19 May 2005, Max Noel wrote:
> On May 19, 2005, at 23:05, Terry Carroll wrote:
>
> > Thanks to you both. I think I may need to step up my "development
> > environment" beyond emacs and a command line.
>
> Actually, if you're having problems with debugging your problem,
> what you
On May 19, 2005, at 23:05, Terry Carroll wrote:
> Thanks to you both. I think I may need to step up my "development
> environment" beyond emacs and a command line.
Actually, if you're having problems with debugging your problem,
what you should step up is your approach to debugging/testi
On Wed, 18 May 2005 [EMAIL PROTECTED] wrote:
> Another possibility is to look at this recipe:
> http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/65287
On Tue, 17 May 2005, Kent Johnson wrote:
> I think this approach to debugging won't scale well and you are just
> seeing the tip of the ic
Terry Carroll wrote:
> I've often found it convenient to run a Python program I'm developing with
> the -i flag. I find it convenient to use as a post-mortem as it hits bugs,
> or to explore data structures.
>
> I've recently started using the construct
>
> if __name__ == "__main__":
>
On Wed, 18 May 2005 [EMAIL PROTECTED] wrote:
> If main is a class, you could change to 'm = main()'; that would at
> least give you access to the class attributes.
Interesting approach; I'm refering to where main() is a method, the usual
python idiom.
__
Quoting Terry Carroll <[EMAIL PROTECTED]>:
> I've recently started using the construct
>
> if __name__ == "__main__":
> main()
>
> And found I can't do the -i thing effectively any more. What's a good
> equivalent approach?
If main is a class, you could change to 'm = main()'; that would at
I've often found it convenient to run a Python program I'm developing with
the -i flag. I find it convenient to use as a post-mortem as it hits bugs,
or to explore data structures.
I've recently started using the construct
if __name__ == "__main__":
main()
And found I can't do the -i
