"JRA" == Jay R Ashworth <jra@baylink.com> writes:
JRA> Got it. I presume SF has release notes, as they're built,
JRA> too?There's moderate release notes in the files view, and of course I try to keep the NEWS file up-to-date, at least with the gross user visible changes. As Thomas can tell you, I'm pretty anal about check-in messages, so when in doubt, cvs log is your best friend. :)
>> Or use the wiki for discussion purposes if you want. The wiki
>> already contains what I think I can get to for 2.1. I want to
>> try to be conservative with changes because the i18n stuff
>> really needs to get out there. Still, I think some of the
>> changes I've made already will help get a bunch of new features
>> into the code base.
JRA> Got it. Well, the code base is pretty clean looking, at
JRA> least the parts I've gotten into, even if my understanding of
JRA> python is not.Thanks! I recently read Richard Gabriel's book and while it was kind of inconsistent, the part I really liked is the idea that code should be habitable. As I concentrate on and rewrite various parts of the code base, I try to keep that in mind.
JRA> Any internals doco written yet? Is their a second tier of
JRA> hackers following the list?Thomas? :)
JRA> And will Python 2 finally get around to showing not only the
JRA> call but the *values* in tracebacks? :-)Oh man, you should have seen Ka-Ping Yee's cgi driver thingie. Among the /many/ cool things he demoed at IPC9 (and it seemed like he demoed a new cool thing every day) was a cgi driver much like Mailman's driver, but which provided an awesome traceback view with values, and probably more. I'm Cc'ing him because I doubt he's on this list. I'm hoping I can prod him into talking more about it. :)
It'd be way cool to adopt either for Python itself or for non-stealthy Mailman tracebacks.
-Barry