(warning: LONG reply)
thanks to those above for the kind remarks. tackling comments
and questions, not quite in chronological order. :-)
> Who would you say the book is aimed at? Advanced programmers?
this book is targeted towards technical professionals already
literate in another high-level
John Coleman wrote:
> John Coleman wrote:
>> John Salerno wrote:
>>> John Coleman wrote:
Greetings,
My copy of the second edition of Chun's "Core Python Programming"
just arrived from Amazon on Friday.
>>> Who would you say the book is aimed at? Advanced programmers? I thought
>>>
John Coleman wrote:
> John Salerno wrote:
> > John Coleman wrote:
> > > Greetings,
> > >My copy of the second edition of Chun's "Core Python Programming"
> > > just arrived from Amazon on Friday.
> >
> > Who would you say the book is aimed at? Advanced programmers? I thought
> > about getting
John Salerno wrote:
> John Coleman wrote:
> > Greetings,
> >My copy of the second edition of Chun's "Core Python Programming"
> > just arrived from Amazon on Friday.
>
> Who would you say the book is aimed at? Advanced programmers? I thought
> about getting it, but I'm not sure if it will be e
John Coleman wrote:
> Greetings,
>My copy of the second edition of Chun's "Core Python Programming"
> just arrived from Amazon on Friday.
Who would you say the book is aimed at? Advanced programmers? I thought
about getting it, but I'm not sure if it will be either 1) too much
repetition of
John Coleman wrote:
> Greetings,
>My copy of the second edition of Chun's "Core Python Programming"
> just arrived from Amazon on Friday. What really jumped out at me is an
> interesting feature about how it sequences its topics, namely,
> (user-defined) functions are not introduced until chapt
I must say I find Wesley Chun's explanations to be most understandable.
I cant' exactly figure out why yet, but he has a way of explaining
something, like, say, decorators, that in minimal words elucidates for
me the intent behind why they are useful. That helps me understand how
they work. I just
...Skimmed through the previous edition.
I don't normally read programming books -- just use the chapters that I
need when I need them, unless of course there is a clever plot twist
coming up ahead (for ex.: "Next: The revenge of lambdas. Will they
stay or will they go?" ;-)
Why? Have you read
I meant "omitted" not as complete omission but as not being there
sooner...
John Coleman wrote:
> A is not ommitted from DBECAFG - it just appears in a non-standard
> order. If the book simply ommitted functions then it would be a
> shocking ommission. As it is, it is just a curious way of sequenc
A is not ommitted from DBECAFG - it just appears in a non-standard
order. If the book simply ommitted functions then it would be a
shocking ommission. As it is, it is just a curious way of sequencing
topics. Functions are in chapter 11 out of 23 chapters - sounds like
the "core" of the book to me.
Nick Vatamaniuc wrote:
> I would consider that an omission. Functions are very important in
> Python. I think the user/reader should see the _def_ and _class_
> statement fairly soon in the introduction. The name of the book is
> thus somewhat misleading, because functions are at the "core" of
>
I would consider that an omission. Functions are very important in
Python. I think the user/reader should see the _def_ and _class_
statement fairly soon in the introduction. The name of the book is
thus somewhat misleading, because functions are at the "core" of
Python.
Functions should be right
Greetings,
My copy of the second edition of Chun's "Core Python Programming"
just arrived from Amazon on Friday. What really jumped out at me is an
interesting feature about how it sequences its topics, namely,
(user-defined) functions are not introduced until chapter 11, fully 400
pages into th
13 matches
Mail list logo
