Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <lh5gua$g05$1@speranza.aioe.org>
References: <9daf0806-02de-4447-964c-c8f8953c23e5@googlegroups.com> <bd158c7b-5511-472c-bce3-cc7b6b7747f6@googlegroups.com> <e2b2b9d5-56bd-4455-b8c3-205000d9acb3@googlegroups.com> <mailman.8369.1395437459.18130.python-list@python.org> <a0403642-c384-4623-bbfd-77c48285ec96@googlegroups.com> <mailman.8377.1395456097.18130.python-list@python.org> <dcd72881-7ee2-4bc3-90ab-7912b4bea05b@googlegroups.com> <lgj4sp$7ed$1@speranza.aioe.org> <532d5bd9$0$29994$c3e8da3$5496439d@news.astraweb.com> <lgoh7j$otg$1@speranza.aioe.org> <mailman.8440.1395651801.18130.python-list@python.org> <lgq8th$nj4$1@speranza.aioe.org> <87ior3w740.fsf@elektro.pacujo.net> <lgqgn7$bpd$1@speranza.aioe.org> <mailman.8478.1395710470.18130.python-list@python.org> <lgqq99$v5j$1@speranza.aioe.org> <lgtsga$2ei$1@dont-email.me> <lh1h1f$ov3$1@speranza.aioe.org> <5334c38e$0$29994$c3e8da3$5496439d@news.astraweb.com> <lh4ouu$n8l$1@speranza.aioe.org> <53364327$0$29994$c3e8da3$5496439d@news.astraweb.com> <lh5gua$g05$1@speranza.aioe.org>
Date: Sat, 29 Mar 2014 15:48:42 +1100
Subject: Re: Explanation of this Python language feature? [x for x in x for x in x] (to flatten a nested list)
From: Chris Angelico <rosuav@gmail.com>
Cc: "python-list@python.org" <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.8682.1396068531.18130.python-list@python.org>
Lines: 37
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:69311

On Sat, Mar 29, 2014 at 3:07 PM, Mark H Harris <harrismh777@gmail.com> wrote:
> You think ~sooo three dimensionally.

Yeah Doc, I have a real problem with that. -- Marty McFly

> Picture this  ~a unicode keyboard with morphing keytops (digital ink, light
> emitting); a standard layout of keys that are touch sensitive, are meta
> operative, and are able to input *every* language on earth (as well any
> symbol). The keyboard may emit light, but not necessarily. The keys may be
> raised, but not necessarily; they have a glassy feel, soft, sensual, and
> completely programmable. Code point pages (key top mappings literally) are
> selectable on|off screen. The keyboard is obviously wireless, and the entire
> keytopsection is mouse-able; the whole keyboard is a pinting device, with
> diff sections for scrolling &c.
>
> This keyboard will be standard in about 25 years... none exist today.

Wrong. You just have to be willing to pay for it.

http://www.thinkgeek.com/product/181d/?srp=14

Or you could just get a blank keytops keyboard and reprogram it how
you like. But hey, have you noticed something? NOT ONE of these ideas
actually makes it easy to write Python code with occasional non-ASCII
characters in it. Switching keyboard mode for a single character is
horribly inefficient, especially if you have to remember a whole lot
of different modes for different characters ("lambda is
meta-butterfly-greek L meta-ctrl-space, and equality is
meta-mathematics 5 meta-ctrl-space"). Putting everything onto a single
keyboard is unworkable. Requiring you to press long key sequences to
generate single characters is useless. (You may as well just press
L-A-M-B-D-A and have it come out as "lambda".) Even with an ideal
keyboard, the creature of your fancies, you won't get past that, for
the same reason that we have keyboards that type letters rather than
English words.

ChrisA