Brett Cannon

(i love the python community, esp the meetings at GOOG HQ. voidspace.org.uk (great dev, great mind, but the un-design, ooh) http://sayspy.blogspot.com/ http://blog.ianbicking.org/ http://jtauber.com/python/ blog.doughellmann.com

Does Zed realize that Guido's response was a joke? http://blip.tv/file/1931026 On a more serious note, I think that high bar to getting things into python is a good thing. What if Zed's changes were accepted, as is, into the Python codebase today? What about when the next guy comes with his alternative APIs for option parsing and email along with a new standard for templates? Should they include them, too? How many completely different APIs for the same thing should they include in the standard library? Any software system as large as Python is going to be imperfect -- it is constrained by backwards compatibility and conflicting requirements. However, Zed is free to build whatever he wants outside the core and make it available to the world. If it catches on enough, maybe his followers will go through the social process to get it into the core. This process helps to ensure consensus, consistency, and quality. For a thoughtful response from a core Python developer, see Brett Cannon's blog post: http://sayspy.blogspot.com/2009/05/staleness-of-standard-library-and.h…

Funnily enough, an hour or so ago I was trying to track down a Python blog I used to enjoy and went on a "This blog has moved merry-go-round... http://sayspy.blogspot.co.uk/2013/07/moving-this-blog-to-medium.html https://medium.com/coder-who-says-py/i-have-moved-over-to-svbtle-564d5… https://nothingbutsnark.svbtle.com/moving-the-blog-to-silvrback And eventually to https://snarky.ca

No home video formats support 48fps, though TVs do. "Both blu-ray and ATSC do not support 48 fps at any resolution. Both do, however, support 60 fps at 720p." http://sayspy.blogspot.com/2011/04/framerates-for-movies-and-debacle-t… Does anyone know if there is newer information or standards planned?

The adoption rate is expected, people should stop complain about the python3 situation when it's not that bad. http://sayspy.blogspot.com/2011/01/my-semi-regular-reminder-that-pytho…

I'm not sure that Python 3 adoption is "slow", per se. We're about halfway through the original adoption timeline. http://sayspy.blogspot.com/2011/01/my-semi-regular-reminder-that-pytho…

Brett and I were just discussing this - and he put up a post summing it up nicely: http://sayspy.blogspot.com/2011/01/my-semi-regular-reminder-that-pytho… Short version? We planned on it taking at least 5 years. Armin's point is that Python 3 isn't "there yet" in terms of demand an adoption. Python 3.2 (which increases performances, and fixes bugs) is just coming out. Armin's point - backed by his comments here, is just that demand isn't high enough for him to dedicate the resources to port. On the other hand, earlier today he was committing bug fixes to the Python 3 source tree, so there's obvious forward movement.

It's too bad they didn't skip to Python 2.7 which seems that will be the last 2.x version [1]. [1] http://sayspy.blogspot.com/2010/10/viewing-python-32-as-successor-to.h…

> Python... [is] on mercurial Welllll... no. Python has made the decision to move to hg, but the conversion has hit some stumbling blocks and is not yet complete: http://sayspy.blogspot.com/2010/01/where-hg-transition-stands.html

http://www.joelonsoftware.com/articles/Unicode.html By the way, python 3000 will force every coder to at least make a conscious decision about the character encoding and will have no none-unicode strings anymore.' [update]Speaking of the devil: http://sayspy.blogspot.com/2008/07/trying-to-make-sense-of-unicode-ter…