Guido’s going to talk about the state of Python. O’Reilly Page. Full coverage is below.
Same presentation as at EuroPython. I’m distracted by my son. he’s sleeping in his hotel room. He will grow up to be whatever he wants.
Python 2.2 was quite a while ago now… last December. [recaps features] We’re working on patching up older versions because sometimes new features break old code. Bugfixes are completely binary-compatible. No new features, no new bugs.
New Python orgs. PSF: board meeting, member meeting, nothing happened. New board and took off. All donations are tax-deductible in the US. Very complicated for other countries. Need more support to be recognized as charity, will likely start campaign after this con.
Python-In-Business: euro-based but basically international group trying to slow changes in Python. Two projects: Python in a Tie, .… Both just branches of secret puthon underediojkkejnkeejkeejme NO CARRIER.
Python in a Tie was result of a stability discussion on c.l.py. Makes conservative users happy. Basically we pick a release and give it a tie. Then we focus on it for along time. Doesn’t mean we’ll stop all development, but one release wears a tie for a given number of months or longer if necessary. May have 2.3 and 2.4 on the road, but 2.2 will still wear the tie. Some people wanted 1.5.2 (laughs.) No, I’m serious!
Kevin Altis: what about modules? will they be upgraded? like the email package? Guido: still discussing, don’t want to add a lot of features. might migrate email package but i’ve been making sure he’s backward compatible and it’s mostly self-contained. Kevin: New modules? Guido: I’m going to be conservative… preferred for those to be third-party packages that can be plugged in.
PBF Compile Farm: Student society forcussed on education, owns a lot of hardware, lets PBF use hardware to test Python on lots of platforms. Run nightly (more often?) cron jobs to build and test Python’s current CVS and reports it to mailing list. Already fixed three or four tiny bugs this way. will build more releases, also including third party packages.
Python Conferences. EuroPython will probably be repeated. Python10 was probably last conference organized by fortech. fortech was probably too expensive, but we’ve joined with UAS to create the YAPyC (Yet antoher python conference) early next year, downtown washington (GWU), going to be very cheap, format more workshop like. expecting 300 people so won’t be totally random. Want to bring hacker atmosphere back. ?: thinking about doing code sprint. getting serious work done as a group. Guido: great idea, doing that for zope3. i blame jim.
Py11 will be at OSCON 2003. that will be like this python track. more biz-oriented. also a small event in the UK. Really looking for organizers. get registration low by relying on volunteers. Need program chairs, etc. don’t even have to come to the conference. organizing BOFs, lightning talks.
HTTP stats. Feb01: 5.5M hits. May02: 8M hits. Enormous number of downloads for latest python. despite biz people, most popular release is always the latest. 70% of distro downloads are always for windows.
Controversy of the Year: to bool or not to bool. I always regretted leaving it out. I left it out because there were already a lot of things and bool sorta didn’t feel necessary. But I always felt bad, ABC had logical value. always expected to put it in when it felt right. All large projects already import True and False self-defined. Also like x==y returning True or False not 0 or 1. also cmp. RPC tools need it for compatibility with other languages. this is for 2.3
Lessons Learned: growth opportunity. (ahem) whn a group is large enough, every topic can be controvertial. lots of misunderstanding about bools. can’t win. simple peps are misunderstood. explanatory peps derided as marketing messages. no way to win, just going to keep ideas to myself.
Python 2.3: technical issues becoming polticial because of the size of the community. people disagree about the righ tthing. no new syntax in python 2.3, except for yield… focusing on library. enumerate(), basestring, import from zip, timeouts for sockets, logging module, gnu_getopt and optional parser, nw compiler, berkleydb module. lots of bug fixes.
PendingDeprecationWarning: poltiical compromise. have to turn it on. Comment: if file is less than 5 secs old, turn it on automatically.
No schedule for 2.3. had one, but didn’t make sense because we were feeature-driven, not time-driven. although some things will be taken if their implementers disappeared off the face of the earth or got a job. PEP will be updated when we know more.
Everyone wants no more new features except their faves. Would you rather? Design problem: iterator next() should it be __next__()? well, user code would do foo.__next__() which seems wrong. realized too late we should have used a builtin function next(iter). poll on newsgroup. poll here: 25 for change, 2 for live with it. Guido: wow, revelation for me.
Have a problem in that there are some failed features which never get retired (backticks, lambda).
Python 3.0: Coming someday, more than two years. What to focus on? Perhaps take zope3 inspiration. start from scratch, small teams and sprints make up new code. [fin]