Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!tudelft.nl!txtfeed1.tudelft.nl!dedekind.zen.co.uk!zen.net.uk!hamilton.zen.co.uk!shaftesbury.zen.co.uk.POSTED!not-for-mail From: Nobody Subject: Re: how to avoid leading white spaces Date: Sat, 04 Jun 2011 21:02:32 +0100 User-Agent: Pan/0.14.2 (This is not a psychotic episode. It's a cleansing moment of clarity.) Message-Id: Newsgroups: comp.lang.python References: <9e861b0e-e768-401b-b5ca-190f20830a08@s9g2000yqm.googlegroups.com> <94ph22FrhvU5@mid.individual.net> <4de8eef1$0$29996$c3e8da3$5496439d@news.astraweb.com> <1237a287-10b0-4a2d-ba35-97b5238deda1@n11g2000yqf.googlegroups.com> <4de992d7$0$29996$c3e8da3$5496439d@news.astraweb.com> <4de9bf50$0$29996$c3e8da3$5496439d@news.astraweb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Lines: 15 Organization: Zen Internet NNTP-Posting-Host: 0059264b.news.zen.co.uk X-Trace: DXC=:5:83mm8L;;YlN:0T[`b8 This fails to support non-ASCII letters, and you know quite well that > having to spell out by hand regexes in both upper and lower (or mixed) > case is not support for case-insensitive matching. That's why Python's re > has a case insensitive flag. I find it slightly ironic that you pointed out the ASCII limitation while overlooking the arbitrariness of upper/lower-case equivalence. Case isn't the only type of equivalence; it's just the only one which affects ASCII. Should we also have flags to treat half-width and full-width characters as equivalent? What about traditional and simplified Chinese, hiragana and katakana, or the various stylistic variants of the Latin and Greek alphabets in the mathematical symbols block (U+1D400..U+1D7FF)?