[Chicago] Chicago Digest, Vol 97, Issue 18

Paul Ebreo paul.ebreo at gmail.com
Wed Sep 25 03:18:40 CEST 2013 

Oren,

You should try IPython on the browser. It is great for teaching

https://www.pythonanywhere.com/try-ipython/

Paul


On Tue, Sep 24, 2013 at 7:59 PM, <chicago-request at python.org> wrote:

> Send Chicago mailing list submissions to
>         chicago at python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://mail.python.org/mailman/listinfo/chicago
> or, via email, send a message with subject or body 'help' to
>         chicago-request at python.org
>
> You can reach the person managing the list at
>         chicago-owner at python.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Chicago digest..."
>
>
> Today's Topics:
>
>    1. Re: Making Website for a Python Class (Yarko Tymciurak)
>    2. Re: Making Website for a Python Class (Ross Heflin)
>    3. Good readings on the history of computing (Jason Wirth)
>    4. Re: Good readings on the history of computing (Matt Foster)
>    5. Re: Good readings on the history of computing (Carl Karsten)
>    6. Re: Good readings on the history of computing (Andy Boyle)
>    7. Re: Good readings on the history of computing (Alex MacKay)
>    8. Re: Good readings on the history of computing (Alex MacKay)
>    9. Re: Good readings on the history of computing (Matt Bone)
>   10. Re: Good readings on the history of computing (Ross Heflin)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 24 Sep 2013 11:56:09 -0500
> From: Yarko Tymciurak <yarkot1 at gmail.com>
> To: The Chicago Python Users Group <chicago at python.org>
> Subject: Re: [Chicago] Making Website for a Python Class
> Message-ID:
>         <CAJ+Z=
> PJzsrfqGrMit7m9rdkKMGALVtkVG2hGG5a79-P-rr9-Xg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> On Tue, Sep 24, 2013 at 11:50 AM, Yarko Tymciurak <yarkot1 at gmail.com>
> wrote:
>
> > and here's the nikola / ipynb solution (note where from):
> >
> >
> >
> http://nbviewer.ipython.org/url/www.damian.oquanta.info/posts/blogging-with-nikola-and-ipython.ipynb
> >
>
>
> read the above link for a sense of just how straightforward doing this
> is...
>
>
>
> >
> >
> >
> > Regards,
> > - Yarko
> >
> >
> > On Tue, Sep 24, 2013 at 11:47 AM, Yarko Tymciurak <yarkot1 at gmail.com
> >wrote:
> >
> >>
> >>
> >> On Tue, Sep 24, 2013 at 11:04 AM, <steve at cugnet.net> wrote:
> >>
> >>>  Why use a ruby app when there is a python one to do the job?
> >>>
> >>> *
> >>>
> http://danielfrg.github.io/blog/2013/02/16/blogging-pelican-ipython-notebook/
> >>> *<
> http://danielfrg.github.io/blog/2013/02/16/blogging-pelican-ipython-notebook/
> >
> >>>
> >>
> >>
> >> Exactly a point I wanted to strongly make:   why teach python, but learn
> >> ruby (and ruby installations):
> >>
> >> There are some excellent python blog engines -
> >>
> >>    - pelican
> >>    - nikola
> >>    - tinkerer (sphinx-based)
> >>
> >>
> >> I knew I'd seen ipython notebook posting in some / one (all?) of these,
> >> so thanks for the link, Steve...
> >>
> >>
> >>
> >>
> >>> To install pelican, just run: pip install pelican
> >>>
> >>
> >> What could be simpler?
> >>
> >>
> >>> ? the pelican ?
> >>>
> >>> *From:* Ross Heflin
> >>> *Sent:* ?Tuesday?, ?September? ?24?, ?2013 ?10?:?54? ?AM
> >>> *To:* The Chicago Python Users Group
> >>>
> >>> Oren,
> >>>
> >>> > redcarpet.h:8:27: fatal error: ruby/encoding.h: No such file or
> >>> directory
> >>> compilation terminated.
> >>>
> >>> I'll take a few minutes and see if I can run this down (in my
> experience
> >>> ruby devs no longer link against 1.9.1 with 1.9.2, 1.9.3 and 2.0.0
> >>> available)
> >>>
> >>> -Ross
> >>>
> >>>
> >>> On Tue, Sep 24, 2013 at 10:37 AM, Oren Livne <livne at uchicago.edu>
> wrote:
> >>>
> >>>>  Dear Ross:
> >>>>
> >>>> jekyll installed well, redcarpet could not find a header file.
> >>>>
> >>>> Oren
> >>>>
> >>>> $ sudo gem install jekyll --no-rdoc --no-ri
> >>>>
> >>>> Successfully installed jekyll-1.2.1
> >>>> 1 gem installed
> >>>> $ sudo gem install redcarpet --no-rdoc --no-ri
> >>>> Building native extensions.  This could take a while...
> >>>> ERROR:  Error installing redcarpet:
> >>>>         ERROR: Failed to build gem native extension.
> >>>>
> >>>>         /usr/bin/ruby1.8 extconf.rb
> >>>> creating Makefile
> >>>>
> >>>> make
> >>>> gcc -I. -I/usr/lib/ruby/1.8/x86_64-linux
> >>>> -I/usr/lib/ruby/1.8/x86_64-linux -I. -D_FORTIFY_SOURCE=2   -fPIC
> >>>> -fno-strict-aliasing -g -g -O2  -fPIC  -fvisibility=hidden  -c
> >>>> html_smartypants.c
> >>>> gcc -I. -I/usr/lib/ruby/1.8/x86_64-linux
> >>>> -I/usr/lib/ruby/1.8/x86_64-linux -I. -D_FORTIFY_SOURCE=2   -fPIC
> >>>> -fno-strict-aliasing -g -g -O2  -fPIC  -fvisibility=hidden  -c
> autolink.c
> >>>> gcc -I. -I/usr/lib/ruby/1.8/x86_64-linux
> >>>> -I/usr/lib/ruby/1.8/x86_64-linux -I. -D_FORTIFY_SOURCE=2   -fPIC
> >>>> -fno-strict-aliasing -g -g -O2  -fPIC  -fvisibility=hidden  -c
> rc_render.c
> >>>> In file included from rc_render.c:17:0:
> >>>> redcarpet.h:8:27: fatal error: ruby/encoding.h: No such file or
> >>>> directory
> >>>> compilation terminated.
> >>>> make: *** [rc_render.o] Error 1
> >>>>
> >>>>
> >>>> Gem files will remain installed in
> >>>> /var/lib/gems/1.8/gems/redcarpet-3.0.0 for inspection.
> >>>> Results logged to
> >>>> /var/lib/gems/1.8/gems/redcarpet-3.0.0/ext/redcarpet/gem_make.out
> >>>>
> >>>>
> >>>> On 9/24/2013 10:24 AM, Ross Heflin wrote:
> >>>>
> >>>>  Oren,
> >>>>
> >>>>  It looks like the gem installed properly, docs just didn't get
> >>>> generated.  try running the binaries that come with jekyll and see
> they're
> >>>> available.  If they aren't run
> >>>>
> >>>> gem install jekyll redcarpet --no-rdoc --no-ri
> >>>>
> >>>>  -Ross
> >>>>
> >>>>
> >>>>  _______________________________________________
> >>>> Chicago mailing listChicago at python.orghttps://
> mail.python.org/mailman/listinfo/chicago
> >>>>
> >>>>
> >>>>
> >>>>  --
> >>>> A person is just about as big as the things that make him angry.
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> Chicago mailing list
> >>>> Chicago at python.org
> >>>> https://mail.python.org/mailman/listinfo/chicago
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> From the "desk" of Ross Heflin
> >>> phone number: (847) <23,504,826th decimal place of pi>
> >>>
> >>> _______________________________________________
> >>> Chicago mailing list
> >>> Chicago at python.org
> >>> https://mail.python.org/mailman/listinfo/chicago
> >>>
> >>>
> >>
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.python.org/pipermail/chicago/attachments/20130924/3d3f5bd3/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Tue, 24 Sep 2013 13:47:00 -0500
> From: Ross Heflin <heflin.rosst at gmail.com>
> To: Oren Livne <livne at uchicago.edu>, The Chicago Python Users Group
>         <chicago at python.org>
> Subject: Re: [Chicago] Making Website for a Python Class
> Message-ID:
>         <CAGy=
> 3C4uJZuTyTCDC-20-j4HgyaA5VMZoPCnnuJVcXvSOiCqeg at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> > Worked like a charm. Thank you so much!
>
> You're quite welcome.
>
> > I am honestly lost in the sea of different options to create a site
>
> Welcome to the world of today, there's a billion options and I have yet to
> pick one myself.
>
> >  I know python well but don't know ruby at all.
>
> I'd recommend just going with a python-based solution so you only have one
> toolset (a devil you already know) to troubleshoot quickly if/when it falls
> over.
>
> > Is there a step-by-step tutorial for newbies for how to create a site
> with jekyll and couple it with a github repo?
>
> If by 'couple with a github repo' you mean hosting on github pages this
> appears after a cursory search: http://jekyllrb.com/docs/github-pages/
> full-on jekyll quickstart is here: http://jekyllrb.com/docs/quickstart/ (I
> should hope it covers some kind of git/github workflow during it!)
>
> My 2c:
> Do some experiments with jekyll and see if it does what you need. HOWEVER
> I'd also strongly recommend the two links sent earlier by Vasily:
> course: https://github.com/vals/scilife-python-course
> retrospective:
> http://nxn.se/post/48156686703/teaching-python-at-scilifelab
>
> Since:
> 1) the author had to skin a similar cat
> 2) he used IPython notebooks which really are a great way to LEARN python
> tool / library usage
> 3) he bothered to writeup a retrospective and make it available, so he's
> hopefully got valuable python-course-teaching knowledge to bestow.
>
> additionally here's a half-hour video on IPython Notebooks from previous
> ChiPy for your reference:
> http://pyvideo.org/video/2195/ipython-notebook-demo
> you'll find quite a few more from previous Pycons at the same site.
>
> I wish you luck in your endeavor, the time has come for me to get back to
> work as I've probably spent too long on this :)
>
> -Ross
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.python.org/pipermail/chicago/attachments/20130924/cd8d5f3e/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Tue, 24 Sep 2013 14:40:16 -0500
> From: Jason Wirth <wirth.jason at gmail.com>
> To: The Chicago Python Users Group <chicago at python.org>
> Subject: [Chicago] Good readings on the history of computing
> Message-ID:
>         <
> CAEwvNMioDY5wduqCXEoZw_c4UGeC6iaQaUHyxvVTg14XRPkY1A at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Whatever the subject I often learn a great deal by studying history and the
> context that spawned the present. For example, my understanding of physics
> grew immensely after learning about the history of science. Technology is
> no different. As much as I think current technology has moved beyond older
> tech, the new always has deep roots in the past. E.g. Python is a newer
> language, so why does PEP8 specify 79 character line widths?
>
> Does anyone have suggestion for articles on the history of computing?
>
> Note, Python specific stuff would be great but it doesn't have to be python
> specific, and almost by definition probably won't be.
>
> For example, here Is a wonderful talk by Douglas Crockford (author of
> JavaScript, the Good Parts) that's exactly the type of material I'm
> interested in.
> http://youtu.be/JxAXlJEmNMg
>
> Another great example is Code.
>
>
>
> --
>
> --
> Jason Wirth
>     213.675.5294
>     wirth.jason at gmail.com
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.python.org/pipermail/chicago/attachments/20130924/2a1b2ea5/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 4
> Date: Tue, 24 Sep 2013 13:12:24 -0700
> From: Matt Foster <matt.foster.c at gmail.com>
> To: The Chicago Python Users Group <chicago at python.org>
> Subject: Re: [Chicago] Good readings on the history of computing
> Message-ID:
>         <
> CAD7Gx8CVoa4RmcBUz1cvUHRBMeEGCRThS-g1u0O0Skg+piFsRw at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> If you're in the mood for a slightly esoteric take on computation, Godel,
> Escher, Bach is a good read. It's more about big ideas than facts and
> history, but will give you some cultural perspective.
>
> -Matt
>
>
> On Tue, Sep 24, 2013 at 12:40 PM, Jason Wirth <wirth.jason at gmail.com>
> wrote:
>
> > Whatever the subject I often learn a great deal by studying history and
> > the context that spawned the present. For example, my understanding of
> > physics grew immensely after learning about the history of science.
> > Technology is no different. As much as I think current technology
> > has moved beyond older tech, the new always has deep roots in the past.
> > E.g. Python is a newer language, so why does PEP8 specify 79 character
> line
> > widths?
> >
> > Does anyone have suggestion for articles on the history of computing?
> >
> > Note, Python specific stuff would be great but it doesn't have to be
> > python specific, and almost by definition probably won't be.
> >
> > For example, here Is a wonderful talk by Douglas Crockford (author of
> > JavaScript, the Good Parts) that's exactly the type of material I'm
> > interested in.
> > http://youtu.be/JxAXlJEmNMg
> >
> > Another great example is Code.
> >
> >
> >
> > --
> >
> > --
> > Jason Wirth
> >     213.675.5294
> >     wirth.jason at gmail.com
> >
> > _______________________________________________
> > Chicago mailing list
> > Chicago at python.org
> > https://mail.python.org/mailman/listinfo/chicago
> >
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.python.org/pipermail/chicago/attachments/20130924/bafde716/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 5
> Date: Tue, 24 Sep 2013 16:49:30 -0500
> From: Carl Karsten <carl at personnelware.com>
> To: The Chicago Python Users Group <chicago at python.org>
> Subject: Re: [Chicago] Good readings on the history of computing
> Message-ID:
>         <CADmzSSjJCd-zanNK7RES7tn620s=
> 27MGoG1iwyAxdajCyUto-A at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Tue, Sep 24, 2013 at 2:40 PM, Jason Wirth <wirth.jason at gmail.com>
> wrote:
> > Python is a newer language
>
> [citation needed]
>
> It is over 20 years old.
>
> granted pep 8:
> http://www.python.org/dev/peps/pep-0008/
> Created:05-Jul-2001
>
> But back to your question about why 79 chars, I think because many of
> us (like me) use text based editors in text based environments like an
> ssh shell that defaults to 80 chars.
>
> and back on topic, you may like this
>
> http://www.youtube.com/watch?v=HCwRGHj5jOE "26 years with Erlang or
> How I got my grey hairs"
>
>
>
> --
> Carl K
>
>
> ------------------------------
>
> Message: 6
> Date: Tue, 24 Sep 2013 17:07:16 -0500
> From: Andy Boyle <andymboyle at gmail.com>
> To: The Chicago Python Users Group <chicago at python.org>
> Subject: Re: [Chicago] Good readings on the history of computing
> Message-ID:
>         <CAHc70yGBw5jzcfdgJkei5yuGWbfjMN++=3yN125kYu=
> ORyTz2Q at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Continuing the off-topic for a moment, for those who are unaware PEP-8 was
> recently updated to allow for longer line length:
> http://www.python.org/dev/peps/pep-0008/#maximum-line-length
>
> "Some teams strongly prefer a longer line length. For code maintained
> exclusively or primarily by a team that can reach agreement on this issue,
> it is okay to increase the nominal line length from 80 to 100 characters
> (effectively increasing the maximum length to 99 characters), provided that
> comments and docstrings are still wrapped at 72 characters."
>
>
> *Andy Boyle | Chicago Tribune*
> News Applications Developer
> @andymboyle | andymboyle.com <http://www.andymboyle.com>
>
>
> On Tue, Sep 24, 2013 at 4:49 PM, Carl Karsten <carl at personnelware.com
> >wrote:
>
> > On Tue, Sep 24, 2013 at 2:40 PM, Jason Wirth <wirth.jason at gmail.com>
> > wrote:
> > > Python is a newer language
> >
> > [citation needed]
> >
> > It is over 20 years old.
> >
> > granted pep 8:
> > http://www.python.org/dev/peps/pep-0008/
> > Created:05-Jul-2001
> >
> > But back to your question about why 79 chars, I think because many of
> > us (like me) use text based editors in text based environments like an
> > ssh shell that defaults to 80 chars.
> >
> > and back on topic, you may like this
> >
> > http://www.youtube.com/watch?v=HCwRGHj5jOE "26 years with Erlang or
> > How I got my grey hairs"
> >
> >
> >
> > --
> > Carl K
> > _______________________________________________
> > Chicago mailing list
> > Chicago at python.org
> > https://mail.python.org/mailman/listinfo/chicago
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.python.org/pipermail/chicago/attachments/20130924/b59873ee/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 7
> Date: Tue, 24 Sep 2013 17:32:39 -0500
> From: Alex MacKay <chicagomackay at gmail.com>
> To: The Chicago Python Users Group <chicago at python.org>
> Subject: Re: [Chicago] Good readings on the history of computing
> Message-ID: <4A24F555-15DB-4C8F-B177-55EAD2EC55EB at gmail.com>
> Content-Type: text/plain; charset=us-ascii
>
> If you are using some process that is based upon original data processing,
> 80 characters is how long a "punch card" used to be.
>
> On Sep 24, 2013, at 4:49 PM, Carl Karsten wrote:
>
> > On Tue, Sep 24, 2013 at 2:40 PM, Jason Wirth <wirth.jason at gmail.com>
> wrote:
> >> Python is a newer language
> >
> > [citation needed]
> >
> > It is over 20 years old.
> >
> > granted pep 8:
> > http://www.python.org/dev/peps/pep-0008/
> > Created:05-Jul-2001
> >
> > But back to your question about why 79 chars, I think because many of
> > us (like me) use text based editors in text based environments like an
> > ssh shell that defaults to 80 chars.
> >
> > and back on topic, you may like this
> >
> > http://www.youtube.com/watch?v=HCwRGHj5jOE "26 years with Erlang or
> > How I got my grey hairs"
> >
> >
> >
> > --
> > Carl K
> > _______________________________________________
> > Chicago mailing list
> > Chicago at python.org
> > https://mail.python.org/mailman/listinfo/chicago
>
>
>
> ------------------------------
>
> Message: 8
> Date: Tue, 24 Sep 2013 17:35:07 -0500
> From: Alex MacKay <chicagomackay at gmail.com>
> To: The Chicago Python Users Group <chicago at python.org>
> Subject: Re: [Chicago] Good readings on the history of computing
> Message-ID: <B651DE1A-B33F-4E85-8D99-061D7A52D259 at gmail.com>
> Content-Type: text/plain; charset="us-ascii"
>
> Again, the 72 is based upon concepts of the 1950's and 1960's.  A old
> punch card was 80 columns long.  The last 8 (73-80) was used for line
> numbering.  If you dropped the deck of cards, you could easily put the
> program, data, back in the correct order.
>
> On Sep 24, 2013, at 5:07 PM, Andy Boyle wrote:
>
> > Continuing the off-topic for a moment, for those who are unaware PEP-8
> was recently updated to allow for longer line length:
> http://www.python.org/dev/peps/pep-0008/#maximum-line-length
> >
> > "Some teams strongly prefer a longer line length. For code maintained
> exclusively or primarily by a team that can reach agreement on this issue,
> it is okay to increase the nominal line length from 80 to 100 characters
> (effectively increasing the maximum length to 99 characters), provided that
> comments and docstrings are still wrapped at 72 characters."
> >
> >
> > Andy Boyle | Chicago Tribune
> > News Applications Developer
> > @andymboyle | andymboyle.com
> >
> >
> > On Tue, Sep 24, 2013 at 4:49 PM, Carl Karsten <carl at personnelware.com>
> wrote:
> > On Tue, Sep 24, 2013 at 2:40 PM, Jason Wirth <wirth.jason at gmail.com>
> wrote:
> > > Python is a newer language
> >
> > [citation needed]
> >
> > It is over 20 years old.
> >
> > granted pep 8:
> > http://www.python.org/dev/peps/pep-0008/
> > Created:05-Jul-2001
> >
> > But back to your question about why 79 chars, I think because many of
> > us (like me) use text based editors in text based environments like an
> > ssh shell that defaults to 80 chars.
> >
> > and back on topic, you may like this
> >
> > http://www.youtube.com/watch?v=HCwRGHj5jOE "26 years with Erlang or
> > How I got my grey hairs"
> >
> >
> >
> > --
> > Carl K
> > _______________________________________________
> > Chicago mailing list
> > Chicago at python.org
> > https://mail.python.org/mailman/listinfo/chicago
> >
> > _______________________________________________
> > Chicago mailing list
> > Chicago at python.org
> > https://mail.python.org/mailman/listinfo/chicago
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.python.org/pipermail/chicago/attachments/20130924/3aea905f/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 9
> Date: Tue, 24 Sep 2013 18:00:42 -0500
> From: Matt Bone <thatmattbone at gmail.com>
> To: The Chicago Python Users Group <chicago at python.org>
> Subject: Re: [Chicago] Good readings on the history of computing
> Message-ID:
>         <
> CAG0VBHvUxMGQ6WjA0z6itW84ePjGXz8a4jJqTVUC4_JEOgCZfQ at mail.gmail.com>
> Content-Type: text/plain; charset=windows-1252
>
> It's not an article, but here's a really old book I love:
>
> http://www.amazon.com/Interactive-Programming-Environments-David-Barstow/dp/0070038856
>
> I think it's interesting to see how little stuff has changed with
> regards to how we actually write programs. This book includes articles
> from notables like Stallman and Kernighan.
>
> I like this thread because earlier today someone sent me an article
> with this quote:
>
> "The lack of interest, the disdain for history is what makes computing
> not-quite-a-field." ? Alan Kay
>
> --matt
>
> On Tue, Sep 24, 2013 at 5:35 PM, Alex MacKay <chicagomackay at gmail.com>
> wrote:
> > Again, the 72 is based upon concepts of the 1950's and 1960's.  A old
> punch
> > card was 80 columns long.  The last 8 (73-80) was used for line
> numbering.
> > If you dropped the deck of cards, you could easily put the program, data,
> > back in the correct order.
> >
> > On Sep 24, 2013, at 5:07 PM, Andy Boyle wrote:
> >
> > Continuing the off-topic for a moment, for those who are unaware PEP-8
> was
> > recently updated to allow for longer line length:
> > http://www.python.org/dev/peps/pep-0008/#maximum-line-length
> >
> > "Some teams strongly prefer a longer line length. For code maintained
> > exclusively or primarily by a team that can reach agreement on this
> issue,
> > it is okay to increase the nominal line length from 80 to 100 characters
> > (effectively increasing the maximum length to 99 characters), provided
> that
> > comments and docstrings are still wrapped at 72 characters."
> >
> >
> > Andy Boyle | Chicago Tribune
> > News Applications Developer
> > @andymboyle | andymboyle.com
> >
> >
> > On Tue, Sep 24, 2013 at 4:49 PM, Carl Karsten <carl at personnelware.com>
> > wrote:
> >>
> >> On Tue, Sep 24, 2013 at 2:40 PM, Jason Wirth <wirth.jason at gmail.com>
> >> wrote:
> >> > Python is a newer language
> >>
> >> [citation needed]
> >>
> >> It is over 20 years old.
> >>
> >> granted pep 8:
> >> http://www.python.org/dev/peps/pep-0008/
> >> Created:05-Jul-2001
> >>
> >> But back to your question about why 79 chars, I think because many of
> >> us (like me) use text based editors in text based environments like an
> >> ssh shell that defaults to 80 chars.
> >>
> >> and back on topic, you may like this
> >>
> >> http://www.youtube.com/watch?v=HCwRGHj5jOE "26 years with Erlang or
> >> How I got my grey hairs"
> >>
> >>
> >>
> >> --
> >> Carl K
> >> _______________________________________________
> >> Chicago mailing list
> >> Chicago at python.org
> >> https://mail.python.org/mailman/listinfo/chicago
> >
> >
> > _______________________________________________
> > Chicago mailing list
> > Chicago at python.org
> > https://mail.python.org/mailman/listinfo/chicago
> >
> >
> >
> > _______________________________________________
> > Chicago mailing list
> > Chicago at python.org
> > https://mail.python.org/mailman/listinfo/chicago
> >
>
>
> ------------------------------
>
> Message: 10
> Date: Tue, 24 Sep 2013 19:53:08 -0500
> From: Ross Heflin <heflin.rosst at gmail.com>
> To: The Chicago Python Users Group <chicago at python.org>
> Subject: Re: [Chicago] Good readings on the history of computing
> Message-ID:
>         <CAGy=3C6r_mm0UkfBMw2vjMtS8vMo=
> kDg17XhNsb6nHEW3OxszA at mail.gmail.com>
> Content-Type: text/plain; charset="windows-1252"
>
> a client once recommended this to me.
> http://www.amazon.com/The-Soul-A-New-Machine/dp/0316491977
> I enjoyed it much
> and no list would be complete without Steven Levy's Hackers: Heroes of the
> Computer Revolution
>
> http://www.amazon.com/Hackers-Computer-Revolution-Anniversary-Edition/dp/1449388396
>
>
>
> On Tue, Sep 24, 2013 at 6:00 PM, Matt Bone <thatmattbone at gmail.com> wrote:
>
> > It's not an article, but here's a really old book I love:
> >
> >
> http://www.amazon.com/Interactive-Programming-Environments-David-Barstow/dp/0070038856
> >
> > I think it's interesting to see how little stuff has changed with
> > regards to how we actually write programs. This book includes articles
> > from notables like Stallman and Kernighan.
> >
> > I like this thread because earlier today someone sent me an article
> > with this quote:
> >
> > "The lack of interest, the disdain for history is what makes computing
> > not-quite-a-field." ? Alan Kay
> >
> > --matt
> >
> > On Tue, Sep 24, 2013 at 5:35 PM, Alex MacKay <chicagomackay at gmail.com>
> > wrote:
> > > Again, the 72 is based upon concepts of the 1950's and 1960's.  A old
> > punch
> > > card was 80 columns long.  The last 8 (73-80) was used for line
> > numbering.
> > > If you dropped the deck of cards, you could easily put the program,
> data,
> > > back in the correct order.
> > >
> > > On Sep 24, 2013, at 5:07 PM, Andy Boyle wrote:
> > >
> > > Continuing the off-topic for a moment, for those who are unaware PEP-8
> > was
> > > recently updated to allow for longer line length:
> > > http://www.python.org/dev/peps/pep-0008/#maximum-line-length
> > >
> > > "Some teams strongly prefer a longer line length. For code maintained
> > > exclusively or primarily by a team that can reach agreement on this
> > issue,
> > > it is okay to increase the nominal line length from 80 to 100
> characters
> > > (effectively increasing the maximum length to 99 characters), provided
> > that
> > > comments and docstrings are still wrapped at 72 characters."
> > >
> > >
> > > Andy Boyle | Chicago Tribune
> > > News Applications Developer
> > > @andymboyle | andymboyle.com
> > >
> > >
> > > On Tue, Sep 24, 2013 at 4:49 PM, Carl Karsten <carl at personnelware.com>
> > > wrote:
> > >>
> > >> On Tue, Sep 24, 2013 at 2:40 PM, Jason Wirth <wirth.jason at gmail.com>
> > >> wrote:
> > >> > Python is a newer language
> > >>
> > >> [citation needed]
> > >>
> > >> It is over 20 years old.
> > >>
> > >> granted pep 8:
> > >> http://www.python.org/dev/peps/pep-0008/
> > >> Created:05-Jul-2001
> > >>
> > >> But back to your question about why 79 chars, I think because many of
> > >> us (like me) use text based editors in text based environments like an
> > >> ssh shell that defaults to 80 chars.
> > >>
> > >> and back on topic, you may like this
> > >>
> > >> http://www.youtube.com/watch?v=HCwRGHj5jOE "26 years with Erlang or
> > >> How I got my grey hairs"
> > >>
> > >>
> > >>
> > >> --
> > >> Carl K
> > >> _______________________________________________
> > >> Chicago mailing list
> > >> Chicago at python.org
> > >> https://mail.python.org/mailman/listinfo/chicago
> > >
> > >
> > > _______________________________________________
> > > Chicago mailing list
> > > Chicago at python.org
> > > https://mail.python.org/mailman/listinfo/chicago
> > >
> > >
> > >
> > > _______________________________________________
> > > Chicago mailing list
> > > Chicago at python.org
> > > https://mail.python.org/mailman/listinfo/chicago
> > >
> > _______________________________________________
> > Chicago mailing list
> > Chicago at python.org
> > https://mail.python.org/mailman/listinfo/chicago
> >
>
>
>
> --
> >From the "desk" of Ross Heflin
> phone number: (847) <23,504,826th decimal place of pi>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mail.python.org/pipermail/chicago/attachments/20130924/758da53e/attachment.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Chicago mailing list
> Chicago at python.org
> https://mail.python.org/mailman/listinfo/chicago
>
>
> ------------------------------
>
> End of Chicago Digest, Vol 97, Issue 18
> ***************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/chicago/attachments/20130924/2e6d1562/attachment-0001.html>

More information about the Chicago mailing list