Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news2.arglkargh.de!news.mixmin.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed2a.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Return-Path: <python@mrabarnett.plus.com>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.035
X-Spam-Evidence: '*H*': 0.93; '*S*': 0.00; 'matches': 0.07; 'subject:Question': 0.07; 'from:addr:mrabarnett.plus.com': 0.16; 'from:addr:python': 0.16; 'from:name:mrab': 0.16; 'message- id:@mrabarnett.plus.com': 0.16; 'received:192.168.1.4': 0.16; 'subject:skip:m 10': 0.16; 'unicode.': 0.16; 'wrote:': 0.18; '>>>': 0.22; 'header:User-Agent:1': 0.23; 'affects': 0.24; 'tend': 0.24; 'header:In-Reply-To:1': 0.27; 'equivalent.': 0.31; 'johnson': 0.35; 'but': 0.35; 'two': 0.37; 'expressed': 0.37; 'to:addr:python-list': 0.38; 'aside': 0.39; 'to:addr:python.org': 0.39; 'even': 0.60; 'utilize': 0.61; 'more': 0.64; 'article': 0.77; 'technically': 0.84; 'rick': 0.93
X-CM-Score: 0.00
X-CNFS-Analysis: v=2.1 cv=OZcWD3jY c=1 sm=1 tr=0 a=0nF1XD0wxitMEM03M9B4ZQ==:117 a=0nF1XD0wxitMEM03M9B4ZQ==:17 a=0Bzu9jTXAAAA:8 a=u9EReRu7m0cA:10 a=fYbsqdoXkfoA:10 a=ihvODaAuJD4A:10 a=IkcTkHD0fZMA:10 a=EBOSESyhAAAA:8 a=4RBUngkUAAAA:8 a=pGLkceISAAAA:8 a=cXx4csAvdgpisRhDrbkA:9 a=QEXdDO2ut3YA:10 a=Bm6qEjDGwGEA:10 a=MSl-tDqOz04A:10
X-AUTH: mrabarnett:2500
Date: Sun, 06 Jul 2014 23:49:23 +0100
From: MRAB <python@mrabarnett.plus.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: python-list@python.org
Subject: Re: Question about metacharacter '*'
References: <1404668474.56075.BPMail_high_noncarrier@web163802.mail.gq1.yahoo.com>
In-Reply-To: <1404668474.56075.BPMail_high_noncarrier@web163802.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.11563.1404686967.18130.python-list@python.org>
Lines: 18
NNTP-Posting-Host: 2001:888:2000:d::a6
X-Trace: 1404686967 news.xs4all.nl 2935 [2001:888:2000:d::a6]:60118
X-Complaints-To: abuse@xs4all.nl
Xref: csiph.com comp.lang.python:74061

On 2014-07-06 18:41, Albert-Jan Roskam wrote:
>
>
>
>>In article <d8f8d76d-0a47-4f59-8f09-da2a44cc1d2e@googlegroups.com>,
>> Rick Johnson <rantingrickjohnson@gmail.com> wrote:
>>
>>> As an aside i prefer to only utilize a "character set" when
>>> nothing else will suffice. And in this case r"[0-9][0-9]*"
>>> can be expressed just as correctly  (and less noisy IMHO) as
>>> r"\d\d*".
>>
>>Even better, r"\d+"
>
> I tend tot do that too, even though technically the two are not perfectly equivalent. With the re.LOCALE flag LC_ctype is also affected, which affects what is captured by \d but not by [0-9]
>
\d also matches more than just [0-9] in Unicode.