PUBLIC MARKS with tag "guido van rossum"

All I want to say is, people lighten up. The style guide can't solve all your problems. You are never going to have all code compliant. Use the style guide when it helps, ignore it when it's in the way.

The software is far from finished. An early version of the GUI and window manager are available, and a few small demo applications: chat, video, two games, and a web browser, and that's about it! The plan is to write all applications in Python (except for the web browser), and a "view source" button should show the Python source for the currently running application. In the tradition of Smalltalk (Alan Kay is on the OLPC board, and has endorsed the project's use of Python) the user should be able to edit any part of a "live" aplication and see the effects of the change immediately in the application's behavior. (A versioned document store will make it possible to roll back disastrous changes.) This is where Krstic wants my help: he hopes I can work magic and implement this feature for Python. I got started right away during the conference, with a reimplementation of python's reload() function that can patch classes and functions in place. Even this small component still has a long way to go; a checkpoint of the work in progress is checked into subversion as part of the Py3k standard library. That's not where the rest of my OLPC work will show up; they use GIT for source control, so I will get to learn that.

New Python 3000 Video and Slides by Guido van Rossum February 26, 2007 Summary Video and powerpoint slides of my recent Python 3000 talks are now online. I gave two versions of a new talk on Python 3000 (a.k.a. Py3k or Python 3.0) recently. The first time, a preview, was on February 14, at Google in Mountain View. It is now up on Google Video (here). The second time was on February 24, at PyCon 2007 in Dallas. The powerpoint slides are now up on python.org (here). (I rearranged the talk a bit based on the feedback I got on the Google talk, so the slides don't exactly match the video, but they are mostly close.) If after viewing these you have questions about the implications for the transition from Python 2.x to Python 3.0, please join us on python-dev (start here). Plans are emerging to add many features to Python 2.6 (which will be released a few months before 3.0) that will ease the transition, e.g. backporting selected Py3k features and (optional) warnings about features that will be gone in 3.0.