FAQ
I started reading the beginning Python book. It is intended for people
who are starting out in the Python world. But it is really
complicated, because he tries to explain, then after a bad explanation
he puts out a bad example. I really recommend NOT reading the book.
For it will make you want not to continue in Python. This is just me
letting the air out of my lungs. No need to reply this is just a
recommendation. Txs for the opportunity .

Search Discussions

  • 7stud at Apr 14, 2007 at 7:00 pm

    On Apr 14, 12:37 pm, "Andre P.S Duarte" wrote:
    I started reading the beginning Python book. It is intended for people
    who are starting out in the Python world. But it is really
    complicated, because he tries to explain, then after a bad explanation
    he puts out a bad example. I really recommend NOT reading the book.
    For it will make you want not to continue in Python. This is just me
    letting the air out of my lungs. No need to reply this is just a
    recommendation. Txs for the opportunity .
    There are several beginning python books. You might want to be a
    little more explicit about the book you are talking about. What is
    the title?
  • James Stroud at Apr 14, 2007 at 10:27 pm

    7stud wrote:
    On Apr 14, 12:37 pm, "Andre P.S Duarte" wrote:

    I started reading the beginning Python book. It is intended for people
    who are starting out in the Python world. But it is really
    complicated, because he tries to explain, then after a bad explanation
    he puts out a bad example. I really recommend NOT reading the book.
    For it will make you want not to continue in Python. This is just me
    letting the air out of my lungs. No need to reply this is just a
    recommendation. Txs for the opportunity .

    There are several beginning python books. You might want to be a
    little more explicit about the book you are talking about. What is
    the title?
    I think he means the Apress book _Beginning_Python_. Funny, though, that
    it gets such good reviews on Amazon. Not every book is meant for every
    student.


    James
  • Readability at Apr 15, 2007 at 7:42 am

    On Apr 14, 2:37 pm, "Andre P.S Duarte" wrote:
    I started reading the beginning Python book. It is intended for people
    who are starting out in the Python world. But it is really
    complicated, because he tries to explain, then after a bad explanation
    he puts out a bad example. I really recommend NOT reading the book.
    For it will make you want not to continue in Python. This is just me
    letting the air out of my lungs. No need to reply this is just a
    recommendation. Txs for the opportunity .
    My experience with technical books of all types is that often you'll
    find some that don't work for you at all, while they'll be great for
    other people. If it is the Apress volume you're talking of, I quite
    like it because its more practical than the Learning Python book from
    o'reilly. Although the one I preferred the most was the online text of
    Dive into Python; http://diveintopython.org/. I can see where you're
    coming from though.


    From http Sun Apr 15 09:51:57 2007
    From: http (Paul Rubin)
    Date: 15 Apr 2007 00:51:57 -0700
    Subject: proposed PEP: iterator splicing
    References: <7xirbyi5d7.fsf_-_@ruckus.brouhaha.com>
    <sijUh.9933$YL5.1408@newssvr29.news.prodigy.net>
    Message-ID: <7xzm5am5wi.fsf@ruckus.brouhaha.com>

    John Nagle <nagle at animats.com> writes:
    Less clutter, and avoids yet another temp variable polluting the namespace.
    Are we in danger of running out of temp variables?
    There is unfortunately no way to contain the scope of a loop index to the
    inside of the loop. Therefore introducing more useless loop indexes creates
    more scorekeeping work and bug attractants. Better to get rid of them.

    From http Sun Apr 15 09:55:09 2007
    From: http (Paul Rubin)
    Date: 15 Apr 2007 00:55:09 -0700
    Subject: tuples, index method, Python's design
    References: <mailman.6186.1176061227.32031.python-list@python.org>
    <slrnf1mg41.cbp.apardon@rcpc42.vub.ac.be>
    <Xns990E641C485CEduncanbooth@127.0.0.1>
    <slrnf1mnbp.cbp.apardon@rcpc42.vub.ac.be>
    <1176200361.260546.280510@n76g2000hsh.googlegroups.com>
    <evg53a$umq$1@sea.gmane.org>
    <740c3aec0704100824m132c45fbi5c4c3ec0c0fa3a67@mail.gmail.com>
    <mailman.6301.1176252507.32031.python-list@python.org>
    <slrnf1rqdk.klv.apardon@rcpc42.vub.ac.be>
    <mailman.6403.1176384231.32031.python-list@python.org>
    <slrnf1sfe3.klv.apardon@rcpc42.vub.ac.be>
    <mailman.6409.1176388672.32031.python-list@python.org>
    <slrnf1ucg4.klv.apardon@rcpc42.vub.ac.be>
    <1176489534.568939.249910@q75g2000hsh.googlegroups.com>
    <7x3b33k0l9.fsf@ruckus.brouhaha.com>
    <1176572775.382873.282850@q75g2000hsh.googlegroups.com>
    <7xr6qmrg4x.fsf@ruckus.brouhaha.com>
    <1176618596.238855.122000@d57g2000hsg.googlegroups.com>
    Message-ID: <7xvefym5r6.fsf@ruckus.brouhaha.com>

    "Rhamphoryncus" <rhamph at gmail.com> writes:
    Indexing cost, memory efficiency, and canonical representation: pick
    two. You can't use a canonical representation (scalar values) without
    some sort of costly search when indexing (O(log n) probably) or by
    expanding to the worst-case size (UTF-32). Python has taken the
    approach of always providing efficient indexing (O(1)), but you can
    compile it with either UTF-16 (better memory efficiency) or UTF-32
    (canonical representation).
    I still don't get it. UTF-16 is just a data compression scheme, right?
    I mean, s[17] isn't the 17th character of the (unicode) string regardless
    of which memory byte it happens to live at? It could be that that accessing
    it takes more than constant time, but that's hidden by the implementation.

    So where does the invariant c==s[s.index(c)] fail, assuming s contains c?
  • Klaas at Apr 16, 2007 at 11:17 pm

    On Apr 14, 11:37 am, "Andre P.S Duarte" wrote:
    I started reading the beginning Python book. It is intended for people
    who are starting out in the Python world. But it is really
    complicated, because he tries to explain, then after a bad explanation
    he puts out a bad example. I really recommend NOT reading the book.
    For it will make you want not to continue in Python. This is just me
    letting the air out of my lungs. No need to reply this is just a
    recommendation. Txs for the opportunity .
    I went ahead and didn't read the book, and I can feel the improvement
    already!

    -Mikw

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppython-list @
categoriespython
postedApr 14, '07 at 6:37p
activeApr 16, '07 at 11:17p
posts5
users5
websitepython.org

People

Translate

site design / logo © 2018 Grokbase