Barry Scott wrote:
I fully support Greg Wards view. If string was removed I'd not update the old code but add in my own string module.
Given the effort you guys went to to keep the C extension protocol the same (in the context of crashing on importing a 1.5 dll into 2.0) I amazed you think that string could be removed...
Could you split the lib into blessed and backward compatibility sections? Then by some suitable mechanism I can choose the compatibility I need?
Oh and as for join obviously a method of a list...
['thats','better'].join(' ')
The above is the way as it is defined for JavaScript. But in JavaScript, the list join method performs an implicit str() on the list elements. As has been discussed some time ago, Python's lists are too versatile to justify a string-centric method. Marc André pointed out that one could do a reduction with the semantics of the "+" operator, but Guido said that he wouldn't like to see [2, 3, 5].join(7) being reduced to 2+7+3+7+5 == 24. That could only be avoided if there were a way to distinguish numeric addition from concatenation. but-I-could-live-with-it - ly y'rs - chris -- Christian Tismer :^) <mailto:tismer@tismer.com> Mission Impossible 5oftware : Have a break! Take a ride on Python's Kaunstr. 26 : *Starship* http://starship.python.net 14163 Berlin : PGP key -> http://wwwkeys.pgp.net PGP Fingerprint E182 71C7 1A9D 66E9 9D15 D3CC D4D7 93E2 1FAE F6DF where do you want to jump today? http://www.stackless.com