[issue10539] Regular expression not checking 'range' element on 1st char in string.

Jamie Murray added the comment: Apologies, sincere and most humble apolgies doh! On 26 Nov 2010 18:51, "Georg Brandl" wrote: > > Georg Brandl added the comment: > > I don't think so; closing as invalid. > > -- > nosy: +georg.brandl > resolution: -> invalid > status: open -> closed > >

[issue10539] Regular expression not checking 'range' element on 1st char in string.

Georg Brandl added the comment: I don't think so; closing as invalid. -- nosy: +georg.brandl resolution: -> invalid status: open -> closed ___ Python tracker ___ __

[issue10539] Regular expression not checking 'range' element on 1st char in string.

Eric Smith added the comment: I'm not sure I understand. The output I get is: f42e6be1-29bf-4f3c-ba58-1ae1d9ca5f88 g42e6be1-29bf-4f3c-ba58-1ae1d9ca5f88 False The first string matches. The second string matches because the leading "g" is being matched by "\w". The third string does not match b

[issue10539] Regular expression not checking 'range' element on 1st char in string.

New submission from Jamie Murray : The first char in a word is omitted from being checked against the 'range' element of the 1st part of this expression. The second char is properly checked to see if it's in range # Desired safe string to expect goodString = "f42e6be1-29bf-4f3c-ba58-1ae1d9ca