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