From: Felix W. <Fel...@gm...> - 2004-07-24 14:33:46
|
Beni Cherniavsky wrote: > Anyway, I really don't see the point in removing a feature because it > doesn't work on all Pythons. OK, we'll leave it. > In fact, if someone knows a particular document is not published to > the world (so that it's always processed in his controlled Python 2.3 > environment) and has used `csv-table` in it, he would be very > displeased if now you drop support for it... That doesn't count, BTW. This is a CVS version, so you shouldn't rely on anything. And anyway, someone who uses a CVS version can easily patch it. >>>> I don't know if there's anything else. > > Some encoding error handlers, IIRC. I'll look at backporting these > too. Cute idea. Can't be too difficult to implement, actually. ... Just checked in a backport. Please review it. If you think it's OK, I'll adjust the documentation (which currently states xmlcharrefreplace only works with Python 2.3). > It's sort of silly but organizations think that old bugs are better > than new ones and most will stick to 2.2 for at least another year... > In fact, that's my private motivation for backporting :-). I found it particularly hard to maintain Python 2.1 support (partly because of the missing nested scopes and partly because no one checked if his changes work with Python 2.1 before commiting them :-) ). So maybe we can continue supporting Python 2.2. -- When replying to my email address, please ensure that the mail header contains 'Felix Wiemann'. http://www.ososo.de/ |