(p.s. needing a way to comment on your blog finally provoked me to actually try out openid for the first time .. hey, it’s pretty neat, isn’t it)

(..and so is google app engine! needing an openid to find a way to comment on your blog finally provoked me to actually try out a google app engine app for the first time..)

[[eta: …and markdown links…]]

Re-reading some old blog posts that I never had time to comment on the first time around.

First of all, thanks for the great story. It had never occurred to me that this is what which does; I don’t think I’m likely to forget it now.

(Now that I think about it, I guess I always thought of which‘s job as “telling me what directory the executable command really lives in” — and never subconsciously equated that with “finding the location of the current script”. I guess it’s probably a very desktop-metaphor-inspired, Windows-3.1-influenced way of seeing things!)

I’m going to have to read this again for some of the details to sink in, but one part that I’m confused by is why you piped the script like that rather than writing an executable .py file? I’m still trying to wrap my head around the fact that it even works (logically it makes perfect sense, it’s just so unfamiliar to me) and I can’t tell if it was a stylistic inclination, a requirement of the scenario somehow (which is where I’m getting all fuzzy on the details) or something else?

-after first submission attempt-

Oh! I see what you’ve got going on here. Yea, I’m sure that works, but seems like a rather annoying solution for the user. Also, I now have to reenter this captcha which is hard enough already.