tag:blogger.com,1999:blog-7821856652257554779.post1467344959726834007..comments2025-09-20T09:27:07.510+02:00Andrzej Krzywdahttp://www.blogger.com/profile/06399276063142826365noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7821856652257554779.post-3597956914900071772007-03-10T03:04:00.000+01:002007-03-10T03:04:00.000+01:00Nice explanation. I like how to clarify what happens in the spiking part.<BR/><BR/>Have you considered using doctests to express the unit tests? I find doctests offers a much more natural expression of what you expect to happen, as if you were doing it interactively in an interpreter, without having to invent new assert_* methods, and makes it easy to mix textual description and code.<BR/><BR/>For example:<BR/><BR/> ...<BR/> >>> len(tabs())<BR/> 2<BR/> >>> tabs()<BR/> ['Faye001.jpg', 'Faye002.jpg']<BR/> ...Bjornhttps://www.blogger.com/profile/02304229888004255106noreply@blogger.comtag:blogger.com,1999:blog-7821856652257554779.post-45628973166487293022007-03-09T16:43:00.000+01:002007-03-09T16:43:00.000+01:00Andrzej -- very nice! You should aggregate your blog into Planet Python (or at least the posts tagged with Python, which you can do these days with Blogger). Fuzzyman sometimes links to your posts, but having your feed on PlanetPython would be even better IMO.<BR/><BR/>GrigGrig Gheorghiuhttps://www.blogger.com/profile/17863511617654196370noreply@blogger.com