Date: Fri, 2 Mar 2001 12:58:49 +0000 (GMT)
From: Michael Hudson email@example.com
Subject: python-dev summary, 2001-02-15 - 2001-03-01
Thanks for all the positive feedback for the last summary!
This is a summary of traffic on the python-dev mailing list
between Feb 15 and Feb 28 (inclusive) 2001. It is intended to
inform the wider Python community of ongoing developments. To
comment, just post to firstname.lastname@example.org or comp.lang.python in
the usual way. Give your posting a meaningful subject line, and if
it's about a PEP, include the PEP number (e.g. Subject: PEP 201 -
Lockstep iteration) All python-dev members are interested in seeing
ideas discussed by the community, so don't hesitate to take a
stance on a PEP if you have an opinion.
This is the second python-dev summary written by Michael Hudson.
Previous summaries were written by Andrew Kuchling and can be found
A slightly quieter week on python-dev. As you can see, most Python
developers are too well-adjusted to post much on weekends. Or
There was a lot of traffic on the bugs, patches and checkins
lists in preparation for the upcoming 2.1b1 release.
* backwards incompatibility *
Most of the posts in the large spike in the middle of the
posting distribution were on the subject of backward compatibility.
One of the unexpected (by those of us that hadn't thought too hard
about it) consequences of nested scopes was that some code using
the dreaded "from-module-import-*" code inside functions became
ambiguous, and the plan was to ban such code in Python 2.1. This
provoked a storm of protest from many quarters, including
python-dev and comp.lang.python. If you really want to read all of
this, start here:
Guido announced that the new nested scopes behaviour would be
opt-in in 2.1, but code that will break in python 2.2 when nested
scopes become the default will produce a warning in 2.1. To get the
new behaviour in a module, one will need to put
from __future__ import nested_scopes
at the top of the module. It is possible this gimmick will be
used to introduce further backwards compatible features in the
* obmalloc *
After some more discussion, including Neil Schemenauer pointing
out that obmalloc might enable him to make the cycle GC faster,
obmalloc was finally checked in.
There's a second patch from Vladimir Marangoz implementing a
memory profiler. (sorry for the long line)
Some of the products that appear on this site are from companies from which QuinStreet receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. QuinStreet does not include all companies or all types of products available in the marketplace.