Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #21634 > unrolled thread
| Started by | Kiuhnm <kiuhnm03.4t.yahoo.it> |
|---|---|
| First post | 2012-03-15 00:34 +0100 |
| Last post | 2012-03-18 18:19 +0000 |
| Articles | 20 on this page of 201 — 36 participants |
Back to article view | Back to comp.lang.python
Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-15 00:34 +0100
Re: Python is readable Arnaud Delobelle <arnodel@gmail.com> - 2012-03-14 23:54 +0000
Re: Python is readable Tony the Tiger <tony@tiger.invalid> - 2012-03-14 19:18 -0500
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-15 11:27 +1100
Re: Python is readable Rick Johnson <rantingrickjohnson@gmail.com> - 2012-03-14 20:02 -0700
Re: Python is readable alex23 <wuwei23@gmail.com> - 2012-03-14 23:23 -0700
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-15 11:44 +0100
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-15 21:50 +1100
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-15 12:27 +0100
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-15 22:47 +1100
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-15 12:59 +0100
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-15 23:21 +1100
Re: Python is readable Ben Finney <ben+python@benfinney.id.au> - 2012-03-15 23:31 +1100
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-15 23:38 +1100
Re: Python is readable Ben Finney <ben+python@benfinney.id.au> - 2012-03-16 00:16 +1100
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-16 00:33 +1100
Re: Python is readable Ben Finney <ben+python@benfinney.id.au> - 2012-03-16 00:50 +1100
RE: Python is readable "Prasad, Ramit" <ramit.prasad@jpmorgan.com> - 2012-03-15 17:43 +0000
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-15 15:16 +0100
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-16 01:29 +1100
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-15 15:37 +0100
Re: Python is readable Roy Smith <roy@panix.com> - 2012-03-15 11:14 -0400
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-16 02:27 +1100
Re: Python is readable Roy Smith <roy@panix.com> - 2012-03-15 11:44 -0400
Re: Python is readable Alec Taylor <alec.taylor6@gmail.com> - 2012-03-16 03:01 +1100
Re: Python is readable Mark Lawrence <breamoreboy@yahoo.co.uk> - 2012-03-15 17:41 +0000
Re: Python is readable Thomas Rachel <nutznetz-0c1b6768-bfa9-48d5-a470-7603bd3aa915@spamschutz.glglgl.de> - 2012-03-15 12:14 +0100
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-15 12:48 +0100
Re: Python is readable Mark Lawrence <breamoreboy@yahoo.co.uk> - 2012-03-15 14:06 +0000
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-15 15:19 +0100
Re: Python is readable Tim Golden <mail@timgolden.me.uk> - 2012-03-15 14:28 +0000
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-15 15:55 +0100
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-16 02:08 +1100
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-15 20:40 +0100
Re: Python is readable Michael Torrie <torriem@gmail.com> - 2012-03-15 16:12 -0600
Re: Python is readable Ben Finney <ben+python@benfinney.id.au> - 2012-03-16 09:35 +1100
Re: Python is readable Arnaud Delobelle <arnodel@gmail.com> - 2012-03-15 23:00 +0000
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-16 00:46 +0100
Re: Python is readable Mark Lawrence <breamoreboy@yahoo.co.uk> - 2012-03-15 23:58 +0000
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-16 12:41 +0100
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-16 00:15 +0000
Re: Python is readable Ben Finney <ben+python@benfinney.id.au> - 2012-03-16 10:57 +1100
Re: Python is readable Robert Kern <robert.kern@gmail.com> - 2012-03-15 15:13 +0000
Re: Python is readable Serhiy Storchaka <storchaka@gmail.com> - 2012-03-15 21:43 +0200
Re: Python is readable Alec Taylor <alec.taylor6@gmail.com> - 2012-03-16 01:17 +1100
Re: Python is readable Duncan Booth <duncan.booth@invalid.invalid> - 2012-03-15 14:23 +0000
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-15 15:30 +0100
Re: Python is readable Robert Kern <robert.kern@gmail.com> - 2012-03-15 14:43 +0000
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-15 16:18 +0100
Re: Python is readable Michael Torrie <torriem@gmail.com> - 2012-03-15 16:17 -0600
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-16 00:32 +0100
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-16 03:55 +0000
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-16 13:10 +0100
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-16 16:48 +0000
Re: Python is readable Michael Torrie <torriem@gmail.com> - 2012-03-16 17:39 -0600
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-17 22:22 +0100
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-17 20:59 +0100
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-18 08:20 +1100
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-17 22:28 +0100
Re: Python is readable Michael Torrie <torriem@gmail.com> - 2012-03-17 17:04 -0600
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-19 12:15 +0100
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-19 11:57 +0000
Re: Python is readable Ben Finney <ben+python@benfinney.id.au> - 2012-03-18 11:42 +1100
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-18 01:36 +0000
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-19 12:34 +0100
Re: Python is readable Lie Ryan <lie.1296@gmail.com> - 2012-03-31 16:56 +1100
Re: Python is readable MRAB <python@mrabarnett.plus.com> - 2012-03-31 18:27 +0100
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-16 01:48 +1100
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-15 16:05 +0100
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-16 02:14 +1100
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-15 23:52 +0000
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-16 14:12 +1100
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-16 13:36 +0100
Re: Python is readable Neil Cerutti <neilc@norwich.edu> - 2012-03-16 12:50 +0000
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-16 13:03 +0000
Re: Python is readable Neil Cerutti <neilc@norwich.edu> - 2012-03-16 13:08 +0000
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-16 16:28 +0000
Re: Python is readable Neil Cerutti <neilc@norwich.edu> - 2012-03-16 17:53 +0000
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-16 18:50 +0000
Re: Python is readable Neil Cerutti <neilc@norwich.edu> - 2012-03-16 19:35 +0000
RE: Python is readable "Prasad, Ramit" <ramit.prasad@jpmorgan.com> - 2012-03-16 20:04 +0000
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-17 21:54 +0100
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-18 00:57 +0000
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-18 12:07 +1100
Re: Python is readable Steven D'Aprano <steve+usenet@pearwood.info> - 2012-03-18 02:05 +0000
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-18 13:15 +1100
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-21 00:57 +0100
Re: Python is readable Mel Wilson <mwilson@the-wire.com> - 2012-03-16 16:01 -0400
Re: Python is readable Ethan Furman <ethan@stoneleaf.us> - 2012-03-16 13:30 -0700
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-17 07:59 +1100
Re: Python is readable Terry Reedy <tjreedy@udel.edu> - 2012-03-17 01:09 -0400
Re: Python is readable Neil Cerutti <neilc@norwich.edu> - 2012-03-19 11:26 +0000
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-19 11:51 +0000
Re: Python is readable Neil Cerutti <neilc@norwich.edu> - 2012-03-19 12:53 +0000
Re: Python is readable Robert Kern <robert.kern@gmail.com> - 2012-03-19 14:38 +0000
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-17 21:23 +0100
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-18 01:46 +0000
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-19 12:44 +0100
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-19 15:27 +0000
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-21 00:27 +0100
Re: Python is readable Thomas Rachel <nutznetz-0c1b6768-bfa9-48d5-a470-7603bd3aa915@spamschutz.glglgl.de> - 2012-03-15 16:41 +0100
Re: Python is readable Duncan Booth <duncan.booth@invalid.invalid> - 2012-03-16 09:30 +0000
Re: Python is readable John Ladasky <ladasky@my-deja.com> - 2012-03-18 14:30 -0700
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-19 09:02 +1100
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-19 01:23 +0000
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-19 15:33 +1100
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-19 13:37 +0000
Re: Python is readable Albert van der Horst <albert@spenarnc.xs4all.nl> - 2012-03-20 12:20 +0000
Re: Python is readable alex23 <wuwei23@gmail.com> - 2012-03-18 20:15 -0700
Re: Python is readable Chris Rebert <clp2@rebertia.com> - 2012-03-18 21:14 -0700
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-20 12:55 -0400
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-20 17:48 +0000
Re: Python is readable Terry Reedy <tjreedy@udel.edu> - 2012-03-20 14:09 -0400
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-20 15:28 -0400
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-21 00:22 +0000
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-20 18:28 -0700
Re: Python is readable Ben Finney <ben+python@benfinney.id.au> - 2012-03-21 13:28 +1100
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-20 19:44 -0700
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-21 15:16 +1100
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-20 21:58 -0700
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-21 16:40 +1100
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-20 23:52 -0700
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-21 17:59 +1100
Re: Python is readable Chris Rebert <clp2@rebertia.com> - 2012-03-21 00:16 -0700
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-21 00:57 -0700
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-21 19:15 +1100
Re: Re: Python is readable Evan Driscoll <driscoll@cs.wisc.edu> - 2012-03-21 11:22 -0500
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-21 09:30 -0700
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-21 14:06 -0400
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-21 18:35 -0700
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-22 08:56 +0000
Re: Python is readable (OT) Jon Clements <joncle@googlemail.com> - 2012-03-22 04:18 -0700
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-22 08:47 -0400
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-22 17:18 +0000
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-22 14:26 -0400
Re: Python is readable Albert van der Horst <albert@spenarnc.xs4all.nl> - 2012-03-29 13:44 +0000
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-29 14:37 -0400
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-30 01:42 +0000
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-29 22:26 -0400
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-30 03:36 +0000
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-30 00:38 -0400
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-30 10:47 +0000
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-30 09:46 -0400
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-31 03:20 +1100
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-30 14:15 -0400
Re: Python is readable Neil Cerutti <neilc@norwich.edu> - 2012-03-30 20:30 +0000
Re: Python is readable alex23 <wuwei23@gmail.com> - 2012-04-01 20:38 -0700
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-31 05:29 +1100
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-30 15:55 -0400
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-31 07:20 +1100
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-30 22:07 -0700
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-04-03 08:06 +1000
Re: Python is readable Dan Sommers <dan@tombstonezero.net> - 2012-03-30 16:51 -0400
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-30 16:58 -0400
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-31 08:45 +1100
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-30 19:01 -0400
Re: Python is readable Terry Reedy <tjreedy@udel.edu> - 2012-03-31 00:03 -0400
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-31 19:05 +1100
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-31 10:43 -0400
Re: Python is readable rusi <rustompmody@gmail.com> - 2012-03-30 11:17 -0700
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-30 09:02 -0700
Re: Python is readable alex23 <wuwei23@gmail.com> - 2012-04-01 20:30 -0700
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-04-01 21:01 -0700
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-29 23:44 -0700
RE: Python is readable "Prasad, Ramit" <ramit.prasad@jpmorgan.com> - 2012-03-30 16:40 +0000
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-30 00:27 -0700
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-23 06:08 +1100
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-23 00:17 +1100
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-22 10:29 -0400
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-22 09:12 -0700
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-22 17:44 +0000
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-22 19:42 -0700
Re: Python is readable rusi <rustompmody@gmail.com> - 2012-03-22 20:20 -0700
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-22 21:16 -0700
Re: Python is readable MRAB <python@mrabarnett.plus.com> - 2012-03-23 04:43 +0000
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-22 23:58 -0700
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-23 00:20 -0400
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-22 08:33 -0700
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-23 06:21 +1100
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-22 15:33 -0400
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-23 06:48 +1100
Re: Python is readable Chris Angelico <rosuav@gmail.com> - 2012-03-23 06:49 +1100
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-21 23:34 +0000
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-21 17:54 -0700
Re: Python is readable Lie Ryan <lie.1296@gmail.com> - 2012-03-31 17:25 +1100
Re: Python is readable Steve Howell <showell30@yahoo.com> - 2012-03-31 09:59 -0700
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-21 00:55 -0400
Re: Python is readable Terry Reedy <tjreedy@udel.edu> - 2012-03-20 16:01 -0400
Re: Python is readable Nathan Rice <nathan.alexander.rice@gmail.com> - 2012-03-20 16:34 -0400
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-21 00:01 +0000
Re: Python is readable Lie Ryan <lie.1296@gmail.com> - 2012-03-31 17:15 +1100
Re: Python is readable Devin Jeanpierre <jeanpierreda@gmail.com> - 2012-03-15 13:51 -0400
Re: Python is readable Arnaud Delobelle <arnodel@gmail.com> - 2012-03-15 20:54 +0000
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-16 02:03 +0000
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-16 01:53 +0000
Re: Python is readable Mark Lawrence <breamoreboy@yahoo.co.uk> - 2012-03-16 02:16 +0000
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-16 13:55 +0100
Re: Python is readable Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2012-03-16 16:25 +0000
Re: Python is readable Kiuhnm <kiuhnm03.4t.yahoo.it> - 2012-03-16 17:58 +0100
RE: Python is readable "Prasad, Ramit" <ramit.prasad@jpmorgan.com> - 2012-03-16 17:01 +0000
Re: Python is readable alister <alister.ware@ntlworld.com> - 2012-03-18 18:19 +0000
Page 1 of 11 [1] 2 3 … 11 Next page →
| From | Kiuhnm <kiuhnm03.4t.yahoo.it> |
|---|---|
| Date | 2012-03-15 00:34 +0100 |
| Subject | Python is readable |
| Message-ID | <4f612b19$0$1379$4fafbaef@reader2.news.tin.it> |
I've just started to read
The Quick Python Book (2nd ed.)
The author claims that Python code is more readable than Perl code and
provides this example:
--- Perl ---
sub pairwise_sum {
my($arg1, $arg2) = @_;
my(@result) = ();
@list1 = @$arg1;
@list2 = @$arg2;
for($i=0; $i < length(@list1); $i++) {
push(@result, $list1[$i] + $list2[$i]);
}
return(\@result);
}
--- Python ---
def pairwise_sum(list1, list2):
result = []
for i in range(len(list1)):
result.append(list1[i] + list2[i])
return result
--- ---
It's quite clear that he knows little about Perl.
Here's what I would've written:
sub pairwise_sum {
my ($list1, $list2) = @_;
my @result;
push @result, $list1->[$_] + $list2->[$_] for (0..@$list1-1);
\@result;
}
Having said that, the Python code is still more readable, so there's no
need to misrepresent Perl that way.
Now I'm wondering whether the author will show me "good" or "bad" Python
code throughout the book. Should I keep reading?
Kiuhnm
[toc] | [next] | [standalone]
| From | Arnaud Delobelle <arnodel@gmail.com> |
|---|---|
| Date | 2012-03-14 23:54 +0000 |
| Message-ID | <mailman.658.1331769273.3037.python-list@python.org> |
| In reply to | #21634 |
On 14 March 2012 23:34, Kiuhnm <kiuhnm03.4t.yahoo.it@mail.python.org> wrote:
> I've just started to read
> The Quick Python Book (2nd ed.)
> The author claims that Python code is more readable than Perl code and
> provides this example:
>
> --- Perl ---
> sub pairwise_sum {
> my($arg1, $arg2) = @_;
> my(@result) = ();
> @list1 = @$arg1;
> @list2 = @$arg2;
> for($i=0; $i < length(@list1); $i++) {
> push(@result, $list1[$i] + $list2[$i]);
> }
> return(\@result);
> }
>
> --- Python ---
> def pairwise_sum(list1, list2):
> result = []
> for i in range(len(list1)):
> result.append(list1[i] + list2[i])
> return result
> --- ---
>
> It's quite clear that he knows little about Perl.
> Here's what I would've written:
>
> sub pairwise_sum {
> my ($list1, $list2) = @_;
> my @result;
> push @result, $list1->[$_] + $list2->[$_] for (0..@$list1-1);
> \@result;
> }
>
> Having said that, the Python code is still more readable, so there's no need
> to misrepresent Perl that way.
> Now I'm wondering whether the author will show me "good" or "bad" Python
> code throughout the book. Should I keep reading?
I don't know this book and there may be a pedagogical reason for the
implementation you quote, but pairwise_sum is probably better
implemented in Python 3.X as:
def pairwise_sum(list1, list2):
return [x1 + x2 for x1, x2 in zip(list1, list2)]
Or in Python 2.X:
from itertools import izip
def pairwise_sum(list1, list2):
return [x1 + x2 for x1, x2 in izip(list1, list2)]
Or even:
from operator import add
def pairwise_sum(list1, list2):
return map(add, list1, list2)
--
Arnaud
[toc] | [prev] | [next] | [standalone]
| From | Tony the Tiger <tony@tiger.invalid> |
|---|---|
| Date | 2012-03-14 19:18 -0500 |
| Message-ID | <QuednSLAxdD9qPzSnZ2dnUVZ8vqdnZ2d@giganews.com> |
| In reply to | #21634 |
On Thu, 15 Mar 2012 00:34:47 +0100, Kiuhnm wrote:
> Should I keep reading?
Probably not.
/Grrr
--
___ ___
(\_--_/) | _ ._ _|_|_ _ |o _ _ ._
( 9 9 ) |(_)| |\/ |_| |(/_ ||(_|(/_|
stripes are forever - as overripe ferrets
[toc] | [prev] | [next] | [standalone]
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2012-03-15 11:27 +1100 |
| Message-ID | <mailman.660.1331771276.3037.python-list@python.org> |
| In reply to | #21634 |
On Thu, Mar 15, 2012 at 10:54 AM, Arnaud Delobelle <arnodel@gmail.com> wrote: > I don't know this book and there may be a pedagogical reason for the > implementation you quote, but pairwise_sum is probably better > implemented in Python 3.X as: > > def pairwise_sum(list1, list2): > return [x1 + x2 for x1, x2 in zip(list1, list2)] Okay, here's something for debate. Should the readability of a language be gauged on the basis of its standard library, or should you be comparing actual code? For instance, a quine in C can be fairly complex and messy, and it can be unobvious what it's doing - but in HQ9+ it's easy. Is it fair to compare on that basis, or should you actually implement the same / equivalent code in each before judging? Of course, that's all without getting into the question of what does "readable" even mean. This has nothing to do with the eternal question of whether it's more readable to use verbose English keywords or cryptic symbols. ChrisA
[toc] | [prev] | [next] | [standalone]
| From | Rick Johnson <rantingrickjohnson@gmail.com> |
|---|---|
| Date | 2012-03-14 20:02 -0700 |
| Message-ID | <8e72d74f-c844-4de3-8a37-f6b1fdc2291f@y27g2000yqy.googlegroups.com> |
| In reply to | #21639 |
On Mar 14, 7:27 pm, Chris Angelico <ros...@gmail.com> wrote: > Okay, here's something for debate. > > Should the readability of a language be gauged on the basis of its > standard library, or should you be comparing actual code? I think the library matters greatly. Yes, one could argue that the same functionality "could" be wrapped-up in the competing language, but then, why has it not already been wrapped? When comparing say, "language A" (WITHOUT a built-in print function) and "Language B" (WITH a built-in print function), would you cry unfairness when B wielded the built-in? > [...] > Of course, that's all without getting into the question of what does > "readable" even mean. One could get caught in an infinite loop of the "Chicken and the Egg" paradox here. However, when we are talking about the Python programming language "readable" simply means: "neophyte readable". That is, "readable to someone with little or no experience with the language". I think that has always been Python's philosophy from the beginning (even all the way back to CP4E!). > This has nothing to do with the eternal question > of whether it's more readable to use verbose English keywords or > cryptic symbols. Again, for the case of Python, cryptic symbols are frowned upon. Of course for the "hacker", cryptic symbols can save keystrokes and white space -- but at the expense of "neophyte readability"! > ChrisA Thanks for reminding me of your name. I had almost forgotten who i replied to ;-)
[toc] | [prev] | [next] | [standalone]
| From | alex23 <wuwei23@gmail.com> |
|---|---|
| Date | 2012-03-14 23:23 -0700 |
| Message-ID | <50e9ceec-40f1-4ead-b2b6-87328b30d084@ow8g2000pbc.googlegroups.com> |
| In reply to | #21644 |
Rick Johnson <rantingrickjohn...@gmail.com> wrote: > However, when we are talking about the Python > programming language "readable" simply means: "neophyte readable". > That is, "readable to someone with little or no experience with the > language". Nonsense. List comprehensions are not immediately obvious to new Python users. The functionality of 'with' requires an understanding of context managers. Python's readability has more to do with simplifying code maintenance. The idea that Python code has to be obvious to non-programmers is an incorrect and dangerous one.
[toc] | [prev] | [next] | [standalone]
| From | Kiuhnm <kiuhnm03.4t.yahoo.it> |
|---|---|
| Date | 2012-03-15 11:44 +0100 |
| Message-ID | <4f61c828$0$1390$4fafbaef@reader2.news.tin.it> |
| In reply to | #21646 |
On 3/15/2012 7:23, alex23 wrote: > Rick Johnson<rantingrickjohn...@gmail.com> wrote: >> However, when we are talking about the Python >> programming language "readable" simply means: "neophyte readable". >> That is, "readable to someone with little or no experience with the >> language". > > Nonsense. List comprehensions are not immediately obvious to new > Python users. The functionality of 'with' requires an understanding of > context managers. Python's readability has more to do with simplifying > code maintenance. Let's try that. Show me an example of "list comprehensions" and "with" (whatever they are). Kiuhnm
[toc] | [prev] | [next] | [standalone]
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2012-03-15 21:50 +1100 |
| Message-ID | <mailman.667.1331808662.3037.python-list@python.org> |
| In reply to | #21651 |
On Thu, Mar 15, 2012 at 9:44 PM, Kiuhnm <kiuhnm03.4t.yahoo.it@mail.python.org> wrote: > Let's try that. > Show me an example of "list comprehensions" and "with" (whatever they are). I'll do a list comp, because they lend themselves well to one-liners. what_am_i = '\n'.join(["%X\t%c"%(i,i) for i in range(128)]) Okay, that one also uses printf formatting, which may be a smidge obscure. Here's a simpler example: what_am_i = [x*x for x in range(11)] ChrisA
[toc] | [prev] | [next] | [standalone]
| From | Kiuhnm <kiuhnm03.4t.yahoo.it> |
|---|---|
| Date | 2012-03-15 12:27 +0100 |
| Message-ID | <4f61d221$0$1375$4fafbaef@reader2.news.tin.it> |
| In reply to | #21652 |
On 3/15/2012 11:50, Chris Angelico wrote:
> On Thu, Mar 15, 2012 at 9:44 PM, Kiuhnm
> <kiuhnm03.4t.yahoo.it@mail.python.org> wrote:
>> Let's try that.
>> Show me an example of "list comprehensions" and "with" (whatever they are).
>
> I'll do a list comp, because they lend themselves well to one-liners.
> what_am_i = '\n'.join(["%X\t%c"%(i,i) for i in range(128)])
A few conjectures:
1) '\n' is an object and join one of its methods;
2) [...] is a list comprehension;
3) that 'for' suggests that range isn't (or doesn't return) a list but
an iterator;
4) points 2 and 3 suggest that [...] builds a list (or array?) by
querying an iterator.
5) "%X\t%"(i,i) is probably equivalent to the C-like Perl's
sprintf("%X\t%c", i, i)
So what_am_i is a simple ASCII table.
> Okay, that one also uses printf formatting, which may be a smidge
> obscure. Here's a simpler example:
>
> what_am_i = [x*x for x in range(11)]
what_am_i = 0, 1, 4, 9, ..., 100
Your first example suggests that range(n) is a sequence iterator which
returns, if queried n times,
0,...,n-1
(which is a bit counterintuitive, IMHO).
Kiuhnm
[toc] | [prev] | [next] | [standalone]
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2012-03-15 22:47 +1100 |
| Message-ID | <mailman.668.1331812073.3037.python-list@python.org> |
| In reply to | #21654 |
On Thu, Mar 15, 2012 at 10:27 PM, Kiuhnm
<kiuhnm03.4t.yahoo.it@mail.python.org> wrote:
> On 3/15/2012 11:50, Chris Angelico wrote:
>> I'll do a list comp, because they lend themselves well to one-liners.
>> what_am_i = '\n'.join(["%X\t%c"%(i,i) for i in range(128)])
>
>
> A few conjectures:
> 1) '\n' is an object and join one of its methods;
> 2) [...] is a list comprehension;
> 3) that 'for' suggests that range isn't (or doesn't return) a list but an
> iterator;
> 4) points 2 and 3 suggest that [...] builds a list (or array?) by querying
> an iterator.
> 5) "%X\t%"(i,i) is probably equivalent to the C-like Perl's
> sprintf("%X\t%c", i, i)
>
> So what_am_i is a simple ASCII table.
Correct. Actually, there's a few differences between Python 2 and 3;
in Py2, range() returns a list, but in Py3 an iterable object. But
'for' will happily iterate over a list.
>> Okay, that one also uses printf formatting, which may be a smidge
>> obscure. Here's a simpler example:
>>
>> what_am_i = [x*x for x in range(11)]
>
> what_am_i = 0, 1, 4, 9, ..., 100
Correct again.
> Your first example suggests that range(n) is a sequence iterator which
> returns, if queried n times,
> 0,...,n-1
> (which is a bit counterintuitive, IMHO).
It's a little odd, perhaps, if seen in a vacuum. But everything counts
from zero - list indices, etc - so it makes sense for range(len(lst))
to return indices valid for lst.
List comps are pretty readable if you know how programming languages
work. Python need not be readable by everyone and his grandmother, and
it does a fairly good job of being grokkable to someone who has a few
ranks in Coding. (Yeah, I'm a D&D nerd. )
ChrisA
[toc] | [prev] | [next] | [standalone]
| From | Kiuhnm <kiuhnm03.4t.yahoo.it> |
|---|---|
| Date | 2012-03-15 12:59 +0100 |
| Message-ID | <4f61d9a2$0$1377$4fafbaef@reader2.news.tin.it> |
| In reply to | #21655 |
On 3/15/2012 12:47, Chris Angelico wrote: > On Thu, Mar 15, 2012 at 10:27 PM, Kiuhnm >> Your first example suggests that range(n) is a sequence iterator which >> returns, if queried n times, >> 0,...,n-1 >> (which is a bit counterintuitive, IMHO). > > It's a little odd, perhaps, if seen in a vacuum. But everything counts > from zero - list indices, etc - so it makes sense for range(len(lst)) > to return indices valid for lst. Maybe range uses [...) intervals? So range(a,b) is a,a+1,a+2,...,b-1 and range(b) is just short-hand for range(0,b)? > List comps are pretty readable if you know how programming languages > work. Python need not be readable by everyone and his grandmother, and > it does a fairly good job of being grokkable to someone who has a few > ranks in Coding. (Yeah, I'm a D&D nerd. ) I like what I've seen so far. Kiuhnm
[toc] | [prev] | [next] | [standalone]
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2012-03-15 23:21 +1100 |
| Message-ID | <mailman.669.1331814092.3037.python-list@python.org> |
| In reply to | #21657 |
On Thu, Mar 15, 2012 at 10:59 PM, Kiuhnm <kiuhnm03.4t.yahoo.it@mail.python.org> wrote: > On 3/15/2012 12:47, Chris Angelico wrote: >> It's a little odd, perhaps, if seen in a vacuum. But everything counts >> from zero - list indices, etc - so it makes sense for range(len(lst)) >> to return indices valid for lst. > > Maybe range uses [...) intervals? So range(a,b) is a,a+1,a+2,...,b-1 and > range(b) is just short-hand for range(0,b)? Yup. It's amazing how accurate your conjectures are - it's almost like you've been reading the docs! :D But yeah, that's pretty logical IMHO; and having gotten used to [) intervals in many areas of computing, I've come to find [] intervals disconcerting. Bible passages are described as, for instance, John 14:5-7, which is a three-verse passage (5, 6, 7), even though 7-5=2. However, inclusive-inclusive intervals have the benefit that they don't require the element "beyond the last" to be indexable. This is important if you're working with something that takes up all of addressable memory - going back to the IBM PCs on which I learned to code, you could use one 64KB segment for an array, but then there's no way for a 16-bit integer to indicate "past the end". >> List comps are pretty readable if you know how programming languages >> work. Python need not be readable by everyone and his grandmother, and >> it does a fairly good job of being grokkable to someone who has a few >> ranks in Coding. (Yeah, I'm a D&D nerd. ) > > I like what I've seen so far. Python has its problems, but it's a good language. I personally prefer to delimit blocks of code with braces than with indentation, and I also prefer explicit declaration of variables (yes, it's extra work, but you can have infinitely nested scopes and easily-caught syntax errors when you misspell one), but they're relatively minor. One of my favorite aspects of Python is that *everything* is an object. There's no magic syntax that gives you a piece of an object, or something special about variables that contain this, that, or the other. A literal list [like, this, one] can be used in exactly the same ways as the name of a variable containing a list or a function call returning a list - there is no difference. Oh how I yearn for that when working in C++ or PHP! ChrisA
[toc] | [prev] | [next] | [standalone]
| From | Ben Finney <ben+python@benfinney.id.au> |
|---|---|
| Date | 2012-03-15 23:31 +1100 |
| Message-ID | <87k42moxkq.fsf@benfinney.id.au> |
| In reply to | #21658 |
Chris Angelico <rosuav@gmail.com> writes: > Yup. It's amazing how accurate your conjectures are - it's almost like > you've been reading the docs! :D But yeah, that's pretty logical IMHO; > and having gotten used to [) intervals in many areas of computing, > I've come to find [] intervals disconcerting. Bible passages are > described as, for instance, John 14:5-7, which is a three-verse > passage (5, 6, 7), even though 7-5=2. Another good reason to advocate for proper typography. “John 14:5–7” indicates a range (because it uses U+2013 EN DASH), whereas “7−5” indicates subtraction (because it uses U+2212 MINUS SIGN). A hyphen (‘-’ U+002D) is inappropriate in either case. -- \ “He that would make his own liberty secure must guard even his | `\ enemy from oppression.” —Thomas Paine | _o__) | Ben Finney
[toc] | [prev] | [next] | [standalone]
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2012-03-15 23:38 +1100 |
| Message-ID | <mailman.671.1331815110.3037.python-list@python.org> |
| In reply to | #21660 |
On Thu, Mar 15, 2012 at 11:31 PM, Ben Finney <ben+python@benfinney.id.au> wrote:
> Another good reason to advocate for proper typography. "John 14:5-7"
> indicates a range (because it uses U+2013 EN DASH), whereas "7-5"
> indicates subtraction (because it uses U+2212 MINUS SIGN). A hyphen ('-'
> U+002D) is inappropriate in either case.
Heh. Yes, but when you're seeking the size of a range, you use
subtraction. The fact that the en dash and minus sign are both often
represented in ASCII with a hyphen is pure coincidence.
ChrisA
[toc] | [prev] | [next] | [standalone]
| From | Ben Finney <ben+python@benfinney.id.au> |
|---|---|
| Date | 2012-03-16 00:16 +1100 |
| Message-ID | <87fwdaovgz.fsf@benfinney.id.au> |
| In reply to | #21662 |
Chris Angelico <rosuav@gmail.com> writes:
> On Thu, Mar 15, 2012 at 11:31 PM, Ben Finney <ben+python@benfinney.id.au> wrote:
> > Another good reason to advocate for proper typography. "John 14:5-7"
> > indicates a range (because it uses U+2013 EN DASH), whereas "7-5"
> > indicates subtraction (because it uses U+2212 MINUS SIGN). A hyphen
> > ('-' U+002D) is inappropriate in either case.
>
> Heh. Yes, but when you're seeking the size of a range, you use
> subtraction.
Not the size of an *inclusive* range, such as a range indicated by use
of an en dash :-)
> The fact that the en dash and minus sign are both often represented in
> ASCII with a hyphen is pure coincidence.
Hopefully, the fact that your quoting of my text munged the characters
down to ASCII is also pure coincidence, and is soon to be corrected at
your end? Or has your client program not joined the rest of us in the
third millennium with Unicode?
--
\ “Geeks like to think that they can ignore politics. You can |
`\ leave politics alone, but politics won't leave you alone.” |
_o__) —Richard M. Stallman, 2002-07-26 |
Ben Finney
[toc] | [prev] | [next] | [standalone]
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2012-03-16 00:33 +1100 |
| Message-ID | <mailman.674.1331818392.3037.python-list@python.org> |
| In reply to | #21665 |
On Fri, Mar 16, 2012 at 12:16 AM, Ben Finney <ben+python@benfinney.id.au> wrote:
> Chris Angelico <rosuav@gmail.com> writes:
>
>> On Thu, Mar 15, 2012 at 11:31 PM, Ben Finney <ben+python@benfinney.id.au> wrote:
>> > Another good reason to advocate for proper typography. "John 14:5-7"
>> > indicates a range (because it uses U+2013 EN DASH), whereas "7-5"
>> > indicates subtraction (because it uses U+2212 MINUS SIGN). A hyphen
>> > ('-' U+002D) is inappropriate in either case.
>>
>> Heh. Yes, but when you're seeking the size of a range, you use
>> subtraction.
>
> Not the size of an *inclusive* range, such as a range indicated by use
> of an en dash :-)
Yes you do, you just have to add one to it. You still use subtraction. :)
>> The fact that the en dash and minus sign are both often represented in
>> ASCII with a hyphen is pure coincidence.
>
> Hopefully, the fact that your quoting of my text munged the characters
> down to ASCII is also pure coincidence, and is soon to be corrected at
> your end? Or has your client program not joined the rest of us in the
> third millennium with Unicode?
It's gmail, and I don't know why it folded everything down. I've told
it to cast everything to text (to avoid the stupid look you sometimes
get with nested replies to HTML-formatted emails), and I guess it
decided to go ASCII. Your mail displayed just fine, it was something
in the reply mechanism.
ChrisA
[toc] | [prev] | [next] | [standalone]
| From | Ben Finney <ben+python@benfinney.id.au> |
|---|---|
| Date | 2012-03-16 00:50 +1100 |
| Message-ID | <87bonyotx2.fsf@benfinney.id.au> |
| In reply to | #21667 |
Chris Angelico <rosuav@gmail.com> writes: > On Fri, Mar 16, 2012 at 12:16 AM, Ben Finney <ben+python@benfinney.id.au> wrote: > > Hopefully, the fact that your quoting of my text munged the > > characters down to ASCII is also pure coincidence, and is soon to be > > corrected at your end? Or has your client program not joined the > > rest of us in the third millennium with Unicode? > > It's gmail, and I don't know why it folded everything down. Ah. The answer is “No”, then. Gmail (from what I can tell of receiving messages from it) is terrible at Unicode, and for that reason among many others is a poor choice for interacting with modern forums. I recommend you add your voice to those complaining at Gmail's support team about poor Unicode support, and meanwhile use a better-maintained free-software client. -- \ “Quidquid latine dictum sit, altum viditur.” (“Whatever is | `\ said in Latin, sounds profound.”) —anonymous | _o__) | Ben Finney
[toc] | [prev] | [next] | [standalone]
| From | "Prasad, Ramit" <ramit.prasad@jpmorgan.com> |
|---|---|
| Date | 2012-03-15 17:43 +0000 |
| Message-ID | <mailman.693.1331834371.3037.python-list@python.org> |
| In reply to | #21668 |
> > > Hopefully, the fact that your quoting of my text munged the > > > characters down to ASCII is also pure coincidence, and is soon to be > > > corrected at your end? Or has your client program not joined the > > > rest of us in the third millennium with Unicode? Outlook showed the EN DASH but your MINUS SIGN and hyphen were the same for me. (UTF-8) Ramit Ramit Prasad | JPMorgan Chase Investment Bank | Currencies Technology 712 Main Street | Houston, TX 77002 work phone: 713 - 216 - 5423 -- This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.
[toc] | [prev] | [next] | [standalone]
| From | Kiuhnm <kiuhnm03.4t.yahoo.it> |
|---|---|
| Date | 2012-03-15 15:16 +0100 |
| Message-ID | <4f61f9bf$0$1381$4fafbaef@reader2.news.tin.it> |
| In reply to | #21658 |
On 3/15/2012 13:21, Chris Angelico wrote: > On Thu, Mar 15, 2012 at 10:59 PM, Kiuhnm > <kiuhnm03.4t.yahoo.it@mail.python.org> wrote: >> On 3/15/2012 12:47, Chris Angelico wrote: >>> It's a little odd, perhaps, if seen in a vacuum. But everything counts >>> from zero - list indices, etc - so it makes sense for range(len(lst)) >>> to return indices valid for lst. >> >> Maybe range uses [...) intervals? So range(a,b) is a,a+1,a+2,...,b-1 and >> range(b) is just short-hand for range(0,b)? > > Yup. It's amazing how accurate your conjectures are - it's almost like > you've been reading the docs! :D Come on... that was easy! :) > But yeah, that's pretty logical IMHO; > and having gotten used to [) intervals in many areas of computing, > I've come to find [] intervals disconcerting. Bible passages are > described as, for instance, John 14:5-7, which is a three-verse > passage (5, 6, 7), even though 7-5=2. Common people use mainly inclusive intervals as far as I can tell. For instance, "from" and "to" are inclusive. They could tell you they don't like your intervals because 8-5+1 = 4 instead of 3. > However, inclusive-inclusive intervals have the benefit that they > don't require the element "beyond the last" to be indexable. This is > important if you're working with something that takes up all of > addressable memory - going back to the IBM PCs on which I learned to > code, you could use one 64KB segment for an array, but then there's no > way for a 16-bit integer to indicate "past the end". But you lose the empty interval (a,a). You're forced to use (a,a-1) or something similar. There's always a drawback. >>> List comps are pretty readable if you know how programming languages >>> work. Python need not be readable by everyone and his grandmother, and >>> it does a fairly good job of being grokkable to someone who has a few >>> ranks in Coding. (Yeah, I'm a D&D nerd. ) >> >> I like what I've seen so far. > > Python has its problems, but it's a good language. I personally prefer > to delimit blocks of code with braces than with indentation, I, on the other hand, prefer indentation. I find braces redundant (in fact, I never use them in pseudo-code). > and I > also prefer explicit declaration of variables (yes, it's extra work, > but you can have infinitely nested scopes and easily-caught syntax > errors when you misspell one), but they're relatively minor. I usually declare my variables but close to where I need them. > One of my > favorite aspects of Python is that *everything* is an object. There's > no magic syntax that gives you a piece of an object, or something > special about variables that contain this, that, or the other. A > literal list [like, this, one] can be used in exactly the same ways as > the name of a variable containing a list or a function call returning > a list - there is no difference. Oh how I yearn for that when working > in C++ or PHP! Don't worry. Soon you'll be using C++0x :))) Kiuhnm
[toc] | [prev] | [next] | [standalone]
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2012-03-16 01:29 +1100 |
| Message-ID | <mailman.678.1331821755.3037.python-list@python.org> |
| In reply to | #21670 |
On Fri, Mar 16, 2012 at 1:16 AM, Kiuhnm <kiuhnm03.4t.yahoo.it@mail.python.org> wrote: > Don't worry. Soon you'll be using C++0x :))) I use gcc/g++ with most of the new features enabled. There's some pretty handy features in it. Frankly, though, if I'd known about Cython when I started the current project, I would have argued to write it all in Python and Cify (is that a word?) the most performance-critical sections afterwards, instead of writing it in C++. It'd be a lot of hassle to change it now, but if anyone else is looking at writing a large project in C "for performance", I would strongly recommend writing in Python or Pike first. (Some day, I'm going to have to actually try Cython. But I know enough of embedding/extending Python to know that the technique would definitely be viable, and Cython can only make it easier.) ChrisA
[toc] | [prev] | [next] | [standalone]
Page 1 of 11 [1] 2 3 … 11 Next page →
Back to top | Article view | comp.lang.python
csiph-web