[Python-Dev] python-dev Summary for 2005-02-01 through 2005-02-14 [draft]

Brett C. bac at OCF.Berkeley.EDU
Fri Mar 4 07:55:47 CET 2005

OK, so this one is really short.  Beyond the fact that I am probably doing this 
too late at night I also want to give the three people who have stepped forward 
to take over for me when I stopped writing the Summaries multiple chances to 
pick up on any of the Skipped Threads or even flesh out any of my thread 
summaries more.  I have asked them to post their writing here to make the 
choosing of a successor a little on the open side.

Hope to send this out Sunday night.


Summary Announcements

Giving myself a gold watch

As some of you may have already heard or read, I am retiring from writing the 
python-dev Summaries after sending out the March 16 - 31 summary.  It has been 
a long time coming and it required a kick in the ass (graciously supplied by 
Steve Holden) to finally make me let go of doing this and let someone else take 

The joy of the Summaries has dwindled over the 2.5 years I have been doing 
this.  I was only doing them to be helpful.  But now I would rather put my time 
and effort I have for Python into coding work rather than the Summaries.  I 
would like to think I can be more productive and helpful as a programmer than a 
writer.  And so there will only be three more regular Summaries after this 
written by yours truly.

But do not worry about the Summaries dying!  When I announced this (see 
http://mail.python.org/pipermail/python-dev/2005-March/051823.html for the 
thread that led to this), three individuals stepped forward to pick up the work 
once I step down.  Steven Bethard, Tony Meyer, and Tim Lesher are being 
considered.  I honestly have no clue how the heck I am going to choose between 
the three of them.

As for my last Summary, expect a more expository one with my random thoughts on 
PyCon, Python, and anything else that comes to mind that I feel like using this 
space to abuse.  You have Scott David Daniels to thank for that format idea for 
my final hurrah.

Go to PyCon!

I just booked my hotel room for PyCon_.  You going to be there so I can shake 
your hand, thanking you for supporting Python?

.. _PyCon: http://www.pycon.org/


Python Security Response Team founded
For those of you who don't know, a security hole was found in XML-RPC servers 
in the stdlib that use register_instance; details at 
http://www.python.org/security/PSF-2005-001/ .

In response to this, Guido has now formed the 'Python Security Response Team`_. 
  This group's job is to respond to any and all security issues that come up as 
quickly as possible and to issue a patch in a timely fashion.

.. _Python Security Response Team: http://www.python.org/security/

Contributing threads:
   - `Wanted: members for Python Security Response Team <>`__

Licensing issues in the stdlib
It was reported to python-dev that 'profiler' and 'md5 do not conform to the 
Debian Free Software Guidelines.  The specific issue was derived works using 
Python.  This is obviously not a good thing.

Things are in the works, though.  The hope is to get the copyrights signed over 
and all of this cleared up.  At worst the modules will be replaced with code 
licensed to the Python Software Foundation.  If you care to accelerate this by 
writing replacements please do so.

Contributing threads:
   - `license issues with profiler.py and md5.h/md5c.c <>`__

Skipped Threads
+ complex I/O problem
+ Is msvcr71.dll re-redistributable?
+ Son of PEP 246, redux
+ Re: PEP 246: LiskovViolation as a name
+ 2.3.5 and 2.4.1 release plans
+ Re: [Python-checkins] python/dist/src/Python future.c, 2.14, 2.15
+ list of constants -> tuple of constants
+ Other library updates
+ Re: python/dist/src/Lib rfc822.py,1.78,1.79
+ Patch review: [ 1098732 ] Enhance tracebacks and stack traces with vars
+ Re: [Python-checkins] python/dist/src/Python compile.c, 2.343, 2.344
+ Re: [Python-checkins] python/dist/src/Lib xmlrpclib.py, 1.38, 1.39
+ ViewCVS on SourceForge is broken
+ builtin_id() returns negative numbers
+ Clarification sought about including a multidimensional array object into 
Python core

More information about the Python-Dev mailing list