I actually have a strong feeling about this. That is, against it. I don't like reload() and think it should be considered a magic you shouldn't touch unless you really need to. I'm under the impression its up for removal, but I hope to keep it in a module somewhere instead, if that is the case. Anyway, to the point. I specifically am against its used in testing interactively, because I think interactively testing things is a poor habit to get into and ways to do that just get in the way of automated testing.
Calvin Spealman | Homepage | 07/05/29 - 1:09 am | #

It's very useful whilst spiking though.

I'm a big fan of automated testing, but thnk that losing reload would be a mistake.
Fuzzyman | Homepage | 07/05/29 - 8:48 am | #

I don't think it's going anywhere. Actually, it will be necessary for the "show source" button to allow code to be edited, in the One Laptop Per Child (olpc) laptop. Looks like xreload is an experimental implementation of reload where all classes and methods in python memory are updated: http://mail.python.org/pipermail...ary/ 007787.html
Kumar McMillan | Homepage | 07/05/29 - 3:35 pm | #