News for hackers. Stuff that matters.
Re:Unfortunate Python by thurn on Monday December 19, 2011 @06:20PM (#3371541)
> If you're debugging at the interactive prompt consider debugging with a small script instead.

I don't understand this suggestion. The ability to interact with my code via the REPL is a very important python feature for me, is the author suggesting I abandon that?

Re:Unfortunate Python by abstractbill on Monday December 19, 2011 @06:37PM (#3371582)
I think the author is just saying if you're debugging something in a REPL and you're finding you need to reload() frequently, then you might want to consider switching to debugging with a small script instead (and of course there's no reason the script couldn't just import the things you're debugging, and then dump you into a REPL).
Re:Unfortunate Python by sitkack on Monday December 19, 2011 @06:44PM (#3371614)
You mean like when I debug a script as

    ipython>import foo as t
    ipython>t.test(10,20)
    ipython>reload t
Roughly 2/3rds of this guy's rant is off base. Maybe if he had flushed out his arguments with citations, but seriously. It is all opinion.

Reasoning with opinion is dumb.

Re:Unfortunate Python by dboat on Monday December 19, 2011 @06:59PM (#3371649)
You did the same thing. What's so bad about reasoning with opinion?
Re:Unfortunate Python by sitkack on Saturday December 24, 2011 @08:00PM (#3390143)
You just got stabbed by an ironicaltite
Re:Unfortunate Python by webexcess on Monday December 19, 2011 @06:39PM (#3371590)
You can use python -i to enter interactive mode after executing a script. Maybe I should clarify that part
Re:Unfortunate Python by kkolev on Tuesday December 20, 2011 @01:32PM (#3374510)
Ooh, dunno why I thought that wasn't supported in IPython too before, but it is. Lovely.