On 5/2/2014 9:15 PM, Chris Angelico wrote:
(My reading of PEP 3131 is that NFKC is used; is that what's
implemented, or was that a temporary measure and/or something for Py2
to consider?)
The 3.4 docs say "The syntax of identifiers in Python is based on the
Unicode standard annex UAX-31, with
On Sat, May 3, 2014 at 12:02 PM, Steven D'Aprano
wrote:
> If you know your victim is reading source code in Ariel font, "rn" and
> "m" are virtually indistinguishable except at very large sizes.
I kinda like the idea of naming it after a bratty teenager who rebels
against her father and runs away
On Sat, 03 May 2014 02:02:32 +, Steven D'Aprano wrote:
> On Fri, 02 May 2014 17:58:51 -0700, Rustom Mody wrote:
>
>> I am confused about the tone however: You think this
>>
> (fine, fine) = (1,2) # and no issue about it
>>
>> is fine?
>
>
> It's no worse than any other obfuscated varia
On Fri, 02 May 2014 17:58:51 -0700, Rustom Mody wrote:
> I am confused about the tone however: You think this
>
(fine, fine) = (1,2) # and no issue about it
>
> is fine?
It's no worse than any other obfuscated variable name:
MOOSE, MO0SE, M0OSE = 1, 2, 3
xl, x1 = 1, 2
If you know your vi
On Saturday, May 3, 2014 7:24:08 AM UTC+5:30, Chris Angelico wrote:
> On Sat, May 3, 2014 at 11:42 AM, Rustom Mody wrote:
> > Two identifiers that to some programmers
> > - can look the same
> > - and not to others
> > - and that the language treats as different
> > is not fine (or fine) to me.
> T
On Sat, May 3, 2014 at 11:42 AM, Rustom Mody wrote:
> Two identifiers that to some programmers
> - can look the same
> - and not to others
> - and that the language treats as different
>
> is not fine (or fine) to me.
The language treats them as the same, though.
ChrisA
--
https://mail.python.or
On Saturday, May 3, 2014 6:48:21 AM UTC+5:30, Ned Batchelder wrote:
> On 5/2/14 8:58 PM, Rustom Mody wrote:
> > On Friday, May 2, 2014 11:37:02 PM UTC+5:30, Peter Otten wrote:
> >> Rustom Mody wrote:
> >>> Just noticed a small thing in which python does a bit better than haskell:
> >>> $ ghci
> >>>
On 5/2/14 8:58 PM, Rustom Mody wrote:
On Friday, May 2, 2014 11:37:02 PM UTC+5:30, Peter Otten wrote:
Rustom Mody wrote:
Just noticed a small thing in which python does a bit better than haskell:
$ ghci
let (fine, fine) = (1,2)
Prelude> (fine, fine)
(1,2)
In case its not apparent, the fi in the
On Sat, May 3, 2014 at 10:58 AM, Rustom Mody wrote:
> You think this
>
(fine, fine) = (1,2) # and no issue about it
>
> is fine?
Not sure which part you're objecting to. Are you saying that this
should be an error:
>>> a, a = 1, 2 # simple ASCII identifier used twice
or that Python should t
On Friday, May 2, 2014 11:37:02 PM UTC+5:30, Peter Otten wrote:
> Rustom Mody wrote:
> > Just noticed a small thing in which python does a bit better than haskell:
> > $ ghci
> > let (fine, fine) = (1,2)
> > Prelude> (fine, fine)
> > (1,2)
> > In case its not apparent, the fi in the first fine is a
In article ,
Denis McMahon wrote:
> Method b:
>
> Use telnet to login to your account on the other server, run the script.
Ugh. I hope nobody is using telnet anymore. Passwords send in plain
text over the network. Bad. All uses of telnet should have long since
been replaced with ssh.
On
On Fri, 02 May 2014 12:55:18 -0700, Bhawani Singh wrote:
> I have created the script till here ..
>
> import os
>
> os.chdir("/var/log")
> fd = open("t1.txt", "r")
> for line in fd:
> if re.match("(.*)(file1)(.*)", line):
> print line,
>
> Output :
>
> file1
>
> --
In article ,
Ben Finney wrote:
> The non-breaking space (â â U+00A0) is frequently used in text to keep
> conceptually inseparable text such as â100Â kmâ from automatic word
> breaks https://en.wikipedia.org/wiki/Non-breaking_space>.
Which, by the way, argparse doesn't honor...
http:/
Marko Rauhamaa writes:
> That reminds me: " " [U+00A0 NON-BREAKING SPACE] is often used between
> numbers and units, for example.
The non-breaking space (“ ” U+00A0) is frequently used in text to keep
conceptually inseparable text such as “100 km” from automatic word
breaks https://en.wikipedia.
On Fri, 02 May 2014 01:11:05 -0700, Ferrous Cranus wrote:
> # retrieve cookie from client's browser otherwise set it try:
> cookie = cookies.SimpleCookie( os.environ.get('HTTP_COOKIE', '') )
> cookieID = cookie['ID'].value
> except:
> cookieID = str( time.time() )
> cookieI
I have created the script till here ..
import os
os.chdir("/var/log")
fd = open("t1.txt", "r")
for line in fd:
if re.match("(.*)(file1)(.*)", line):
print line,
Output :
file1
this script i ran on the linux server, but now i want to run this script from
anothe
Rustom Mody wrote:
> Just noticed a small thing in which python does a bit better than haskell:
> $ ghci
> let (fine, fine) = (1,2)
> Prelude> (fine, fine)
> (1,2)
> Prelude>
>
> In case its not apparent, the fi in the first fine is a ligature.
>
> Python just barfs:
Not Python 3:
Python 3.3.2+
On 5/2/14 12:50 PM, Rustom Mody wrote:
Just noticed a small thing in which python does a bit better than haskell:
$ ghci
let (fine, fine) = (1,2)
Prelude> (fine, fine)
(1,2)
Prelude>
In case its not apparent, the fi in the first fine is a ligature.
Python just barfs:
>>>fine = 1
File "", lin
On 05/02/2014 10:50 AM, Rustom Mody wrote:
> Python just barfs:
>
fine = 1
> File "", line 1
> fine = 1
> ^
> SyntaxError: invalid syntax
>
> The point of that example is to show that unicode gives all kind of
> "Aaah! Gotcha!!" opportunities that just dont exist in the old wor
On 2014-05-02 09:08, Steven D'Aprano wrote:
On Thu, 01 May 2014 21:42:21 -0700, Rustom Mody wrote:
Whats the best cure for headache?
Cut off the head
o_O
I don't think so.
Whats the best cure for Unicode?
Ascii
Unicode is not a problem to be solved.
The inability to write standard h
On Friday, May 2, 2014 5:25:37 PM UTC+5:30, Steven D'Aprano wrote:
> On Fri, 02 May 2014 03:39:34 -0700, Rustom Mody wrote:
> > On Friday, May 2, 2014 2:15:41 PM UTC+5:30, Steven D'Aprano wrote:
> >> On Thu, 01 May 2014 19:02:48 -0700, Rustom Mody wrote:
> >> > - Worst of all what we
> >> > *dont*
On 2014-05-02 03:39, Ben Finney wrote:
Rustom Mody writes:
Yes, the headaches go a little further back than Unicode.
Okay, so can you change your article to reflect the fact that the
headaches both pre-date Unicode, and are made much easier by Unicode?
There is a certain large old book...
On Friday, May 2, 2014 5:25:37 PM UTC+5:30, Steven D'Aprano wrote:
> On Fri, 02 May 2014 03:39:34 -0700, Rustom Mody wrote:
> > On Friday, May 2, 2014 2:15:41 PM UTC+5:30, Steven D'Aprano wrote:
> >> On Thu, 01 May 2014 19:02:48 -0700, Rustom Mody wrote:
> >> > - Worst of all what we
> >> > *dont*
On 2014-05-02 19:08, Chris Angelico wrote:
> This is another area where Unicode has given us "a great improvement
> over the old method of giving satisfaction". Back in the 1990s on
> OS/2, DOS, and Windows, a missing glyph might be (a) blank, (b) a
> simple square with no information, or (c) copie
Steven D'Aprano :
> And you've never been bitten by an invisible control character in
> ASCII text? You've lived a sheltered life!
That reminds me: " " (nonbreakable space) is often used between numbers
and units, for example.
Marko
--
https://mail.python.org/mailman/listinfo/python-list
On Fri, 02 May 2014 03:39:34 -0700, Rustom Mody wrote:
> On Friday, May 2, 2014 2:15:41 PM UTC+5:30, Steven D'Aprano wrote:
>> On Thu, 01 May 2014 19:02:48 -0700, Rustom Mody wrote:
>> > - Worst of all what we
>> > *dont* see -- how many others dont see what we see?
>
>> Again, this a deficiency
On Fri, 02 May 2014 19:01:44 +1000, Chris Angelico wrote:
> On Fri, May 2, 2014 at 6:08 PM, Steven D'Aprano
> wrote:
>> ... even *Americans* cannot represent all their common characters in
>> ASCII, let alone specialised characters from mathematics, science, the
>> printing industry, and law.
>
On Friday, May 2, 2014 2:15:41 PM UTC+5:30, Steven D'Aprano wrote:
> On Thu, 01 May 2014 19:02:48 -0700, Rustom Mody wrote:
> > - Worst of all what we
> > *dont* see -- how many others dont see what we see?
> Again, this a deficiency of the font. There are very few code points in
> Unicode which
Ben Finney :
>> Aside: What additional characters does law use that aren't in ASCII?
>> Section § and paragraph ¶ are used frequently, but you already
>> mentioned the printing industry. Are there other symbols?
>
> ASCII does not contain “©” (U+00A9 COPYRIGHT SIGN) nor “®” (U+00AE
> REGISTERED SI
Chris Angelico writes:
> (common with dingbats fonts). With Unicode, the standard is to show
> a little box *with the hex digits in it*. Granted, those boxes are a
> LOT more readable for BMP characters than SMP (unless your text is
> huge, six digits in the space of one character will make them p
On Wednesday, 30 April 2014 20:38:07 UTC+2, Joseph L. Casale wrote:
> > I don't know how to do that stuff in python. Basically, I'm trying to pull
> > certain data from the
> > xml file like the node-name, source, destination and the capacity. Since, I
> > am done with that
> > part, I now want
On Fri, May 2, 2014 at 7:16 PM, Ben Finney wrote:
> Chris Angelico writes:
>
>> On Fri, May 2, 2014 at 6:08 PM, Steven D'Aprano
>> wrote:
>> > ... even *Americans* cannot represent all their common characters in
>> > ASCII, let alone specialised characters from mathematics, science,
>> > the pri
Chris Angelico writes:
> On Fri, May 2, 2014 at 6:08 PM, Steven D'Aprano
> wrote:
> > ... even *Americans* cannot represent all their common characters in
> > ASCII, let alone specialised characters from mathematics, science,
> > the printing industry, and law.
>
> Aside: What additional charact
On Fri, May 2, 2014 at 6:45 PM, Steven D'Aprano
wrote:
>> - unicode 'number-boxes' (what are these called?)
>
> They are missing character glyphs, and they have nothing to do with
> Unicode. They are due to deficiencies in the text font you are using.
>
> Admittedly with Unicode's 0x10 possibl
On Fri, May 2, 2014 at 6:08 PM, Steven D'Aprano
wrote:
> ... even *Americans* cannot represent all their common characters in
> ASCII, let alone specialised characters from mathematics, science, the
> printing industry, and law.
Aside: What additional characters does law use that aren't in ASCII?
On Thu, 01 May 2014 19:02:48 -0700, Rustom Mody wrote:
> I dont know how one causally connects the 'headaches' but Ive seen -
> mojibake
Mojibake is certainly more common with multiple encodings, but the
solution to that is Unicode, not ASCII.
In fact, in your blog post you even link to a post
On Thu, 01 May 2014 21:57:57 +0100, Adam Funk wrote:
> On 2014-05-01, Terry Reedy wrote:
>
>> On 4/30/2014 7:46 PM, Ian Kelly wrote:
>>
>>> It also works if your starting point is (precisely) the north pole. I
>>> believe that's the canonical answer to the riddle, since there are no
>>> bears in
On Thu, 01 May 2014 21:42:21 -0700, Rustom Mody wrote:
> Whats the best cure for headache?
>
> Cut off the head
o_O
I don't think so.
> Whats the best cure for Unicode?
>
> Ascii
Unicode is not a problem to be solved.
The inability to write standard human text in ASCII is a problem, e.g.
38 matches
Mail list logo
