Stephen J. Turnbull wrote: > *Python* does the right thing: it leaves the line break character(s) > in place. It's not Python's problem if programmers go around > stripping characters just because they happen to be at the end of the > line.
But currently you *know* that, e.g. string.strip() will only ever remove whitespace and \n characters, so if those don't matter to you, it's safe to use it. I would be worried if it started removing characters that it didn't remove before, because that could alter the semantics of my code. > Those characters are > mandatory breaks because the expectation is *very* consistent (they > say). I object to being told by the Unicode committee what semantics I should be using for ASCII characters that pre-date unicode by a long way. -- Greg _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
