Comments on: Dive Into Python 3: The Foreword

By: jnoller

jnoller — Wed, 28 Oct 2009 08:00:56 +0000

Any text in the foreword is under the same license as the book itself! Go for it!

By: jnoller

jnoller — Wed, 28 Oct 2009 03:00:56 +0000

Any text in the foreword is under the same license as the book itself! Go for it!

By: Giulio Piancastelli

Giulio Piancastelli — Tue, 27 Oct 2009 17:31:31 +0000

I have translated Dive Into Python 3 in Italian and I would like both to translate also your foreword and to put it alongside the book's translated text. First question: am I allowed to do it? Both the original and the translated book's text are licensed under CC-BY-SA 3.0. So, second question: have you attached / do you want to attach a specific content license to the foreword text as published on this page? (Possibly, a license that would allow me to translate it and publish it on similar terms?) Thanks!

By: jnoller

jnoller — Tue, 27 Oct 2009 01:10:58 +0000

Thank you; again

By: Thijs

Thijs — Tue, 27 Oct 2009 01:02:10 +0000

There's another 'foreward' typo in the first sentence of this blogpost..

By: jnoller

jnoller — Mon, 26 Oct 2009 13:06:43 +0000

Why are you bustin my balls? ;)

Actually, juggling work-work with open-source work and being a parent is a painful process for me, honestly. It doesn't help I'm a severe workaholic. I'd be perfectly fine with 12 hour workdays :|

By: Brian K. Jones

Brian K. Jones — Mon, 26 Oct 2009 12:35:46 +0000

Jesse,

Great foreword, but just one little thing:

If you're coding *between* your daughter's naps (e.g., when she's awake), what are you doing *during* her naps (when she's asleep)? And when do you find time to spend with her?

;-P

Congrats on the honor, and my experience "diving into" python mirrors yours.
brian

By: jnoller

jnoller — Mon, 26 Oct 2009 11:48:59 +0000

I already read Guido's proposal – I volunteered to draft the PEP (it's in progress) for the moratorium. I know that the 2/3 split will mark a pause – I'm for pausing. Being in core dev, my boogeyman has been the standard library – I'd like to see more focus on that, improving, cleaning, testing and other areas outside of the syntax and builtins.

It will be interesting ;)

By: jnoller

jnoller — Mon, 26 Oct 2009 11:46:22 +0000

Argh. Fixed.

By: tag

tag — Mon, 26 Oct 2009 09:09:49 +0000

Great intro, Jesse. It comes at a time when I'm reassessing Python 3 (nearly a year since the first official release) and what it means for the language. I hope to post these thoughts on my own blog soon. In the meantime:

Python 3 also doesn’t end the evolution of the language – not by any stretch. New features, syntax and libraries are still being added, and will probably be added, tweaked and removed for as long as Python itself lives on.

You will have read Guido van Rossum's recent proposal which recommends a moratorium on changes to Python syntax. He also says:

The main goal of the Python development community at this point should be to get widespread acceptance of Python 3000.

Reading between the lines, I think the Python 2/3 fork will mark a significant pause in the evolution of the language. The overhead of developing, supporting and maintaining two versions of everything is high. New features would have to be backported. Libraries need to work on two platforms. Alternative implementations have two targets. Etc.

I'm interested to see how things pan out. Certainly, it's refereshing to read a book like Mark Pilgrim's, which really does dive right in.