Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Mark H Harris
On 3/25/14 12:08 AM, Chris Angelico wrote: How quickly can you switch, type one letter (to generate one Cyrillic character), and switch back? ... very fast. Is not this nicer? >>> Π = pi >>> >>> sin(Π/4) 0.7071067811865475 >>> >>> cos(Π/4) 0.7071067811865476 >>> my pdeclib constants exte

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Rustom Mody
On Tuesday, March 25, 2014 10:38:43 AM UTC+5:30, Chris Angelico wrote: > On Tue, Mar 25, 2014 at 4:00 PM, Rustom Mody wrote: > > Its already there -- and even easier > > Switch to cyrillic-jis-russian (whatever that is!) > > and I get л from k Л from K > How quickly can you switch, type one letter

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Chris Angelico
On Tue, Mar 25, 2014 at 4:14 PM, Mark H Harris wrote: > On 3/25/14 12:08 AM, Chris Angelico wrote: > >> How quickly can you switch, type one letter (to generate one Cyrillic >> character), and switch back? > > > ... very fast. > > Is not this nicer? > Π = pi sin(Π/4) > 0.70710678118

Re: Explanation of this Python language feature? [x for x in x for x in x] (to flatten a nested list)

2014-03-24 Thread Steven D'Aprano
On Tue, 25 Mar 2014 06:57:19 +1100, Chris Angelico wrote: > Can you imagine a high level language without a simple notation for > variable assignment? Certainly not. I don't know... what a stack based or concatenative language like Forth, Postscript, Joy or Factor count as high-level? I'm prett

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Rustom Mody
On Tuesday, March 25, 2014 10:44:42 AM UTC+5:30, Mark H. Harris wrote: > On 3/25/14 12:08 AM, Chris Angelico wrote: > > How quickly can you switch, type one letter (to generate one Cyrillic > > character), and switch back? > ... very fast. > Is not this nicer? > >>> Π = pi > >>> sin(Π/4) > 0

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Chris Angelico
On Tue, Mar 25, 2014 at 4:23 PM, Rustom Mody wrote: > So let me talk of which input methods I use -- devanagari and tex. > I have devanagari-itrans set up in emacs as default (other) input method > So Ctrl-\ (ie 1½ keystrokes) puts emacs into devanagari mode Yes, but putting emacs into a differen

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Mark H Harris
On 3/25/14 12:27 AM, Chris Angelico wrote: my pdeclib constants extension will have alternate spellings for Π and Γ and Δ and others... That's good! (Although typing Π quicker than pi is majorly pushing it. Well, I'll tell ya, its exactly the same--- two key-strokes, believe it or not.

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Mark H Harris
On 3/25/14 12:28 AM, Rustom Mody wrote: π = pi sin(π/4) 0.7071067811865475 cos(π/4) 0.7071067811865476 Looks better in emacs Input with tex mode -- 1 char to switch slightly verbose to type -- \pi gives π \Pi gives Π Whoohoo... yes, way more betterer/ :) -- https://mail.python.org/mailma

Re: Question about Source Control

2014-03-24 Thread Frank Millman
"Rustom Mody" wrote in message news:19d3ddc9-0fb9-476d-a117-e5f174eca...@googlegroups.com... > On Monday, March 17, 2014 6:36:33 PM UTC+5:30, Frank Millman wrote: >> Hi all > >> I know I *should* be using a Source Control Management system, but at >> present I am not. I tried to set up Mercurial

Re: Explanation of this Python language feature? [x for x in x for x in x] (to flatten a nested list)

2014-03-24 Thread Chris Angelico
On Tue, Mar 25, 2014 at 4:28 PM, Steven D'Aprano wrote: > On Tue, 25 Mar 2014 06:57:19 +1100, Chris Angelico wrote: > >> Can you imagine a high level language without a simple notation for >> variable assignment? Certainly not. > > I don't know... what a stack based or concatenative language like

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Rustom Mody
On Tuesday, March 25, 2014 11:04:40 AM UTC+5:30, Mark H. Harris wrote: > On 3/25/14 12:27 AM, Chris Angelico wrote: > >> my pdeclib constants extension will have alternate spellings for Π and > >> Γ > >> and Δ and others... > > That's good! (Although typing Π quicker than pi is majorly pushing

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Chris Angelico
On Tue, Mar 25, 2014 at 4:34 PM, Mark H Harris wrote: > Because the character selector is up on the gui (for me, far left) and the > two strokes are {mouse click the Π } and {mouse click the insert}; rather > than {p} {i} . There is of course a brief time-lag because my right hand > has to move t

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Mark H Harris
On 3/25/14 12:42 AM, Rustom Mody wrote: You are not counting mouse For an emacs user Looking at mouse counts as 3 keystrokes ha! I would not be surprised that just "thinking" about the mouse might be worth 3 key-strokes for an emacs user! I use vi all the time; emacs less; depends on the

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Steven D'Aprano
On Tue, 25 Mar 2014 14:57:02 +1100, Chris Angelico wrote: > On Tue, Mar 25, 2014 at 2:43 PM, Rustom Mody > wrote: >> What you are missing is that programmers spend 90% of their time >> reading code >> 10% writing code >> >> You may well be in the super-whiz category (not being sarcastic here) >>

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Chris Angelico
On Tue, Mar 25, 2014 at 4:42 PM, Rustom Mody wrote: > You are not counting mouse > For an emacs user > Looking at mouse counts as 3 keystrokes > Touching is more like 5-8 > https://sites.google.com/site/steveyegge2/effective-emacs I think the cost of the mouse varies according to technology. I'm

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Mark H Harris
On 3/25/14 12:48 AM, Chris Angelico wrote: Yup. Welcome to timezones. I'm UTC +11 here, although we'll drop back to +10 shortly as DST finishes (yay!). It's currently 0547 UTC, so you're presumably five hours behind UTC, which would put you east coast USA, most likely. (Especially since your mail

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Mark H Harris
On 3/25/14 12:48 AM, Chris Angelico wrote: (Especially since your mailer is putting the dates as mm/dd/yy, which is an abomination peculiar to Americans.) I did not know that; so is 25 Mar 2014 the preferred way? marcus -- https://mail.python.org/mailman/listinfo/python-list

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Steven D'Aprano
On Tue, 25 Mar 2014 15:19:50 +1100, Chris Angelico wrote: > On Tue, Mar 25, 2014 at 2:59 PM, Mark H Harris > wrote: >> I personally think the answer is extended key maps triggered by meta >> keys shift ctrl opt alt command | which call up full alternate >> mappings of Greek|Latin|Math|symbols &c

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Steven D'Aprano
On Tue, 25 Mar 2014 00:14:42 -0500, Mark H Harris wrote: > On 3/25/14 12:08 AM, Chris Angelico wrote: > >> How quickly can you switch, type one letter (to generate one Cyrillic >> character), and switch back? > > ... very fast. > > Is not this nicer? > > >>> Π = pi That's the product operato

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Chris Angelico
On Tue, Mar 25, 2014 at 4:47 PM, Steven D'Aprano wrote: > On Tue, 25 Mar 2014 14:57:02 +1100, Chris Angelico wrote: >> No, I'm not missing that. But the human brain is a tokenizer, just as >> Python is. Once you know what a token means, you comprehend it as that >> token, and it takes up space in

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Rustom Mody
On Tuesday, March 25, 2014 11:17:51 AM UTC+5:30, Steven D'Aprano wrote: > On Tue, 25 Mar 2014 14:57:02 +1100, Chris Angelico wrote: > > wrote: > >> What you are missing is that programmers spend 90% of their time > >> reading code > >> 10% writing code > >> You may well be in the super-whiz catego

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Chris Angelico
On Tue, Mar 25, 2014 at 4:56 PM, Mark H Harris wrote: > On 3/25/14 12:48 AM, Chris Angelico wrote: >> >> Yup. Welcome to timezones. I'm UTC +11 here, although we'll drop back >> to +10 shortly as DST finishes (yay!). It's currently 0547 UTC, so >> you're presumably five hours behind UTC, which wou

Re: Explanation of this Python language feature? [x for x in x for x in x] (to flatten a nested list)

2014-03-24 Thread Steven D'Aprano
On Mon, 24 Mar 2014 18:44:37 -0500, Mark H Harris wrote: > On 3/24/14 6:01 PM, Chris Angelico wrote: > >> Easy fix. Use the "explicit capture" notation: > >> adders[n] = lambda a, n=n: a+n > >> And there you are, out of your difficulty at once! > > Yes, yes, yes, and example: > > adder

Re: Explanation of this Python language feature? [x for x in x for x in x] (to flatten a nested list)

2014-03-24 Thread Steven D'Aprano
On Mon, 24 Mar 2014 17:58:11 -0600, Ian Kelly wrote: > On Mon, Mar 24, 2014 at 3:43 PM, Mark H Harris > wrote: >>Aside from the sin of spelling out "lambda," >> should be ( \x y -> x + y ) a b ) but, neither here nor >> there... > > Well no, it *should* be λx y . x + y but app

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Chris Angelico
On Tue, Mar 25, 2014 at 5:04 PM, Steven D'Aprano wrote: >> I can get up a character map on any platform fairly easily, and if not, >> I can always Google the name of the character I want and copy and paste >> from fileformat.info or some other handy site. It's not that hard. But >> if I want to sa

Re: Explanation of this Python language feature? [x for x in x for x in x] (to flatten a nested list)

2014-03-24 Thread Steven D'Aprano
On Mon, 24 Mar 2014 19:16:15 -0500, Mark H Harris wrote: > On 3/24/14 7:11 PM, Chris Angelico wrote: >> On Tue, Mar 25, 2014 at 10:56 AM, Mark H Harris >> wrote: >>> What is needed is the explicit closure "grab" recommended by ChrisA. >> >> Which does work. You do know why, right? > > Sure. ...

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Chris Angelico
On Tue, Mar 25, 2014 at 5:10 PM, Rustom Mody wrote: > Something that Chris may relate to: > > You type a music score into lilypond > Then call lilypond to convert it into standard western staff notation > > Why not put up the lilypond (ASCII) directly on the piano/organ when you play? > > This is

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Rustom Mody
On Tuesday, March 25, 2014 11:42:50 AM UTC+5:30, Chris Angelico wrote: > On Tue, Mar 25, 2014 at 4:47 PM, Steven D'Aprano wrote: > > On Tue, 25 Mar 2014 14:57:02 +1100, Chris Angelico wrote: > >> No, I'm not missing that. But the human brain is a tokenizer, just as > >> Python is. Once you know wha

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Rustom Mody
On Tuesday, March 25, 2014 12:03:24 PM UTC+5:30, Chris Angelico wrote: > On Tue, Mar 25, 2014 at 5:10 PM, Rustom Mody wrote: > > Something that Chris may relate to: > > You type a music score into lilypond > > Then call lilypond to convert it into standard western staff notation > > Why not put up

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Chris Angelico
On Tue, Mar 25, 2014 at 5:35 PM, Rustom Mody wrote: > I dont think we are anywhere near making real suggestions for real changes > which would need to talk of compatibility, portability, editor support > and all such other good stuff. > > Just a bit of brainstorming to see how an alternative pytho

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Mark H Harris
On 3/25/14 12:08 AM, Chris Angelico wrote: How quickly can you switch, type one letter (to generate one Cyrillic character), and switch back? Ok.. after installing Ukelete from Summer Institute of Linguistics SIL I can now edit the installed keymaps and select them from input sources at the t

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Chris Angelico
On Tue, Mar 25, 2014 at 5:41 PM, Rustom Mody wrote: > ALl of which is isomorphic to Steven's point that forty is less > eyeballable than 40 > > And mine that ∅ is more eyeballable than set([]) I don't disagree that it is; the short tokens are easier to read in quantity. I just don't think that it

Re: Time we switched to unicode? (was Explanation of this Python language feature?)

2014-03-24 Thread Rustom Mody
On Tuesday, March 25, 2014 12:15:11 PM UTC+5:30, Chris Angelico wrote: > On Tue, Mar 25, 2014 at 5:35 PM, Rustom Mody wrote: > > I dont think we are anywhere near making real suggestions for real changes > > which would need to talk of compatibility, portability, editor support > > and all such oth

Re: Explanation of this Python language feature? [x for x in x for x in x] (to flatten a nested list)

2014-03-24 Thread Steven D'Aprano
On Mon, 24 Mar 2014 21:39:33 -0500, Mark H Harris wrote: > On 3/24/14 8:20 PM, Terry Reedy wrote: >> On 3/24/2014 7:56 PM, Mark H Harris wrote: > >>> the list which is used for each of the adder[] functions created. >> >> Wrong. Functions look up global and nonlocal names, such as n, when the >>

<    1   2