python-dev Summary for 2005-05-16 through 2005-05-31[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-05-16_2005-05-31.html]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Summary Announcements
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
----
QOTF
----
We have our first ever Quote of the Fortnight (QOTF), thanks to
the wave of discussion over `PEP 343`_ and Jack Diederich:
I still haven't gotten used to Guido's heart-attack inducing early
enthusiasm for strange things followed later by a simple
proclamation I like. Some day I'll learn that the sound of
fingernails on the chalkboard is frequently followed by candy for
the whole class.
See, even threads about anonymous block statements can end happily! ;)
... _PEP 343: http://www.python.org/peps/pep-0343.html
Contributing thread:
- `PEP 343 - Abstract Block Redux
<http://mail.python.org/pipermail/python-dev/2005-May/053828.html>`__
[SJB]
------------------
First PyPy Release
------------------
The first release of `PyPy`_, the Python implementation of Python, is
finally available. The PyPy team has made impressive progress, and
the current release of PyPy now passes around 90% of the Python
language regression tests that do not depend deeply on C-extensions.
The PyPy interpreter still runs on top of a CPython interpreter
though, so it is still quite slow due to the double-interpretation
penalty.
... _PyPy: http://cod...
python-dev Summary for 2005-05-16 through 2005-05-31[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-05-16_2005-05-31.html]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Summary Announcements
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
----
QOTF
----
We have our first ever Quote of the Fortnight (QOTF), thanks to
the wave of discussion over `PEP 343`_ and Jack Diederich:
I still haven't gotten used to Guido's heart-attack inducing early
enthusiasm for strange things followed later by a simple
proclamation I like. Some day I'll learn that the ...
python-dev Summary for 2005-01-01 through 2005-01-15This is a summary of traffic on the `python-dev mailing list`_ from January 01,
2005 through January 15, 2005. It is intended to inform the wider Python
community of on-going developments on the list. To comment on anything
mentioned here, just post to `comp.lang.python`_ (or email
python-list@python.org which is a gateway to the newsgroup) with a subject line
mentioning what you are discussing. All python-dev members are interested in
seeing ideas discussed by the community, so don't hesitate to take a stance on
something. And if all of this really interests you then get involved and join
`python-dev`_!
This is the fifty-sixth summary written by Brett Cannon (I don't want to do my
homework).
To contact me, please send email to brett at python.org ; I do not have the
time to keep up on comp.lang.python and thus do not always catch follow-ups
posted there.
All summaries are archived at http://www.python.org/dev/summary/ .
Please note that this summary is written using reStructuredText_ which can be
found at http://docutils.sf.net/rst.html . Any unfamiliar punctuation is
probably markup for reST_ (otherwise it is probably regular expression syntax
or a typo =); you can safely ignore it, although I suggest learning reST; it's
simple and is accepted for `PEP markup`_ and gives some perks for the HTML
output. Also, because of the wonders of programs that like to reformat text, I
cannot guarantee you will be able to run ...
python-dev Summary for 2005-01-01 through 2005-01-15This is a summary of traffic on the `python-dev mailing list`_ from January 01,
2005 through January 15, 2005. It is intended to inform the wider Python
community of on-going developments on the list. To comment on anything
mentioned here, just post to `comp.lang.python`_ (or email
python-list@python.org which is a gateway to the newsgroup) with a subject line
mentioning what you are discussing. All python-dev members are interested in
seeing ideas discussed by the community, so don't hesitate to take a stance on
something. And if all of this really interests you then get involved and join
`python-dev`_!
This is the fifty-sixth summary written by Brett Cannon (I don't want to do my
homework).
To contact me, please send email to brett at python.org ; I do not have the
time to keep up on comp.lang.python and thus do not always catch follow-ups
posted there.
All summaries are archived at http://www.python.org/dev/summary/ .
Please note that this summary is written using reStructuredText_ which can be
found at http://docutils.sf.net/rst.html . Any unfamiliar punctuation is
probably markup for reST_ (otherwise it is probably regular expression syntax
or a typo =); you can safely ignore it, although I suggest learning reST; it's
simple and is accepted for `PEP markup`_ and gives some perks for the HTML
output. Also, because of the wonders of programs that like to reformat text, I
cannot guarantee you will be able to run the text version of this ...
python-dev Summary for 2005-12-01 through 2005-12-15[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-12-01_2005-12-15.html]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Announcements
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
-----------------------------------------------------
Reminder: plain text documentation fixes are accepted
-----------------------------------------------------
Want to help out with the Python documentation? Don't know LaTeX? No
problem! Plain text or ReST fixes are also welcome. You won't be able
to produce a diff file like with a normal patch, but comments that
explain how to fix the docs are just as good. A form like "in section
XXX right before the paragraph starting with YYY, the documentation
should say ZZZ" will make it easy for the doc maintainers to apply
your fix.
Contributing thread:
- `c.l.p post on docs
<http://mail.python.org/pipermail/python-dev/2005-December/058479.html>`__
[SJB]
--------------------------------------------
New-style exceptions patch requesting review
--------------------------------------------
With `PEP 352`_ ready_ for Guido's pronouncement, Michael Hudson has
asked for a few more developers to review his patch_ to make all
exceptions new-style. It should be basically ready, but it would be
nice to have a few eyes for sanity checks, documentation, and
compilations on the various platforms.
... _PEP 352: http://www.python.org/peps/pep-0352.html
... _ready: htt...
python-dev Summary for 2005-03-01 through 2005-03-15[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-03-01_2005-03-15.html]
=====================
Summary Announcements
=====================
-----------------------------
Second to last summary for me
-----------------------------
Just a reminder, after this Summary there is only one more left for me to
write. After that Tim Lesher, Tony Meyer, and Steven Bethard will be taking over.
-----------------
See you at PyCon!
-----------------
PyCon_ is practically upon us! If you are going to be there, great! Please
feel free to say hello if you run int...
python-dev Summary for 2005-08-01 through 2005-08-15[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-08-01_2005-08-15.html]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Announcements
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
----------------------------
QOTF: Quote of the Fortnight
----------------------------
Some wise words from Donovan Baarda in the PEP 347 discussions:
It is true that some well designed/developed software becomes =
reliable
very quickly. However, it still takes heavy use over time to prove that.
Contributing thread:
- `PEP: Migrating the Python CVS to Subversion
<http://mail.python.org/pipermail/python-dev/2005-August/055105.html>`__
[SJB]
------------
Process PEPs
------------
The PEP editors have introduced a new PEP category: "Process", for PEPs =
that
don't fit into the "Standards Track" and "Informational" categories. =
More
detail can be found in `PEP 1`_, which is itself a Process PEP.
... _PEP 1: http://www.python.org/peps/pep-0001.html
Contributing thread:
- `new PEP type: Process
<http://mail.python.org/pipermail/python-dev/2005-August/055361.html>`__
[TAM]
-----------------------------------------------
Tentative Schedule for 2.4.2 and 2.5a1 Releases
-----------------------------------------------
Python 2.4.2 is tentatively scheduled for a mid-to-late September =
release
and a first alpha of Python 2.5 for March 2006 (with a final release =
aro...
python-dev summary for 2005-07-01 to 2005-07-15[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-07-01_2005-07-15.html]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Announcements
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
------------------------------
QOTF (Quotes of the Fortnight)
------------------------------
Marc-Andre Lemburg provides perhaps the best summary to date of `how
strings and Unicode should be used`_ in Python:
To untie this Gordian Knot, we should use strings and Unicode like
they are supposed to be used (in the context of text data):
* strings are fine for text data that is encod...
python-dev Summary for 2005-08-01 through 2005-08-15[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-08-01_2005-08-15.html]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Announcements
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
----------------------------
QOTF: Quote of the Fortnight
----------------------------
Some wise words from Donovan Baarda in the PEP 347 discussions:
It is true that some well designed/developed software becomes =
reliable
very quickly. However, it still takes heavy use over time to prove that.
Contributing thread:
- `PEP: Migrating the Python CVS to Subversion
<http://mail.p...
python-dev Summary for 2005-09-01 to 2005-09-15[Note: yes, this is *September*! All my (Tony's) bad, Steve has been =20=
chugging away at the summaries like he should have. Extra apologies =20
for this one - it was approved by python-dev a while back, and I =20
didn't realise that I hadn't done the python-list post.]
python-dev Summary for 2005-09-01 through 2005-09-15
++++++++++++++++++++++++++++++++++++++++++++++++++++
... contents::
[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-09-01_2005-09-15.html]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Announcements
=3D=3D=3D=3D=3D=3D=3...
python-dev Summary for 2005-04-01 through 2005-04-15[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-04-01_2005-04-15.html]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Summary Announcements
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
---------------------------
New python-dev summary team
---------------------------
This summary marks the first by the team of Steve Bethard, Tim Lesher,
and Tony Meyer. We're trying a collaborative approach to the
summaries: each fortnight, we'll be getting together in a virtual
smoke-filled back room to divide up ...
python-dev Summary for 2005-12-01 through 2005-12-15[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-12-01_2005-12-15.html]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Announcements
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
-----------------------------------------------------
Reminder: plain text documentation fixes are accepted
-----------------------------------------------------
Want to help out with the Python documentation? Don't know LaTeX? No
problem! Plain text or ReST fixes are also welcome. You won't be able
to produce a diff file like with a normal patch, but comments that
explain how t...
python-dev Summary for 2005-03-01 through 2005-03-15[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-03-01_2005-03-15.html]
=====================
Summary Announcements
=====================
-----------------------------
Second to last summary for me
-----------------------------
Just a reminder, after this Summary there is only one more left for me to
write. After that Tim Lesher, Tony Meyer, and Steven Bethard will be taking over.
-----------------
See you at PyCon!
-----------------
PyCon_ is practically upon us! If you are going to be there, great! Please
feel free to say hello if you run into me (will be at the sprints and the
conference Wednesday and Thursday; skipping Friday to see a friend). Always
happy to stop-and-chat.
... _PyCon: http://www.pycon.org/
------------------------
2.4.1 should be out soon
------------------------
Python 2.4c2 has now been released. Assuming no major issues come up, 2.4
final will be out March 29; day after PyCon.
But in order to make sure no issues come up, we need the code to be tested!
Please get the code and run the regression tests. If you are on a UNIX system
it is as easy as running ``make test`` (``make testall`` is even better). The
tests can also be run on non-UNIX systems; see
http://docs.python.org/lib/regrtest.html on how.
=========
Summaries
=========
----------------------
2.4 should be out soon
----------------------
Python 2.4.1c1 was releaseed, but enough bug...
python-dev Summary for 2005-06-01 through 2005-06-15[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-06-01_2005-06-15.html]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Summary Announcements
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
---------------------------------
Bug Day: Saturday, June 25th 2005
---------------------------------
AMK organized another `Python Bug Day`_ on Saturday, June 25th. Hope
you got a chance to help out!
... _Python Bug Day: http://wiki.python.org/moin/PythonBugDay
Contributing Threads:
- `Bug day on the 25th?
<http://mail.python....
python-dev summary for 2005-07-01 to 2005-07-15[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-07-01_2005-07-15.html]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Announcements
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
------------------------------
QOTF (Quotes of the Fortnight)
------------------------------
Marc-Andre Lemburg provides perhaps the best summary to date of `how
strings and Unicode should be used`_ in Python:
To untie this Gordian Knot, we should use strings and Unicode like
they are supposed to be used (in the context of text data):
* strings are fine for text data that is encoded using the default encod=
ing
* Unicode should be used for all text data that is not or cannot be
encoded in the default encoding
Later on in Py3k, all text data should be stored in Unicode and all
binary data in some new binary type.
On a more entertaining note, Anthony Baxter describes the general
outlook outlook on handling `threads vs signals`_:
threads vs signals is a platform-dependant trail of misery,
despair, horror and madness
... _how strings and Unicode should be used:
http://mail.python.org/pipermail/python-dev/2005-July/054854.html
... _threads vs signals:
http://mail.python.org/pipermail/python-dev/2005-July/054832.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D
Summaries
=3D=3D=3D=3D=3D=3D=3D=3D=3D
---------------------------------------
PEP 343 Documentation: Context Managers
---------------------------------------
Raymo...
python-dev Summary for 2006-05-01 through 2006-05-15python-dev Summary for 2006-05-01 through 2006-05-15
++++++++++++++++++++++++++++++++++++++++++++++++++++
... contents::
[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2006-05-01_2006-05-15]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Announcements
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
-------------------
Python 2.5 progress
-------------------
Python 2.5 is moving steadily towards its first beta release. See
`PEP 356`_ for more details and the full schedule.
... _PEP 356: http://www.python.org/dev/peps/pep-0356/
Contributing threads:
- `2.5 open issues
<http://mail.python.org/pipermail/python-dev/2006-May/064965.html>`__
- `nag, nag -- 2.5 open issues
<http://mail.python.org/pipermail/python-dev/2006-May/064966.html>`__
----------------------------------------------------------
Experimental wiki for editing the Python library reference
----------------------------------------------------------
Fredrik Lundh introduced his `pyref wiki`_ which allows wiki-style
editing of the Python Library Reference. In addition to providing
useful links, like unique URLs for all keywords, types and special
methods, the project aims to make cleaning up and rewriting parts of
the Python documentation as easy as editing a wiki. If you'd like to
help out, let `Fredrik`_ know your infogami user name and he can add
you to the group.
... _pyref wiki: http://pyref.infogami.com/
... _Fredrik:...
python-dev Summary for 2005-09-01 to 2005-09-15[Note: yes, this is *September*! All my (Tony's) bad, Steve has been =20=
chugging away at the summaries like he should have. Extra apologies =20
for this one - it was approved by python-dev a while back, and I =20
didn't realise that I hadn't done the python-list post.]
python-dev Summary for 2005-09-01 through 2005-09-15
++++++++++++++++++++++++++++++++++++++++++++++++++++
... contents::
[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-09-01_2005-09-15.html]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Announcements
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
-----------------------------
QOTF: Quotes of the Fortnight
-----------------------------
In the thread on the print statement, Charles Cazabon provided some =20
nice imagery for Guido's Python 3.0 strategy. Our first QOTF is his =20
comment about the print statement:
It's an anomaly. It stands out in the language as a sore thumb =20
waiting for Guido's hammer.
We also learned something important about the evolution of Python =20
thanks to Paul Moore. In the thread on the Python 3.0 executable =20
name, Greg Ewing worried that if the Python 3.0 executable is named =20
"py":
Python 4.0 is going to just be called "p", and by the time we =20
get to Python 5.0, the name will have vanished altogether!
Fortunately, as Paul Moore explains in our second QOTF, these naming =20
convention...
python-dev Summary for 2005-06-01 through 2005-06-15[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-06-01_2005-06-15.html]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Summary Announcements
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
---------------------------------
Bug Day: Saturday, June 25th 2005
---------------------------------
AMK organized another `Python Bug Day`_ on Saturday, June 25th. Hope
you got a chance to help out!
... _Python Bug Day: http://wiki.python.org/moin/PythonBugDay
Contributing Threads:
- `Bug day on the 25th?
<http://mail.python.org/pipermail/python-dev/2005-June/054126.html>`__
[SJB]
----------------------
FishEye for Python CVS
----------------------
Peter Moore has kindly set up `Fish Eye for the Python CVS repository`_.
FishEye is a repository browsing, searching, analysis and monitoring tool,
with great features like RSS feeds, Synthetic changesets, Pretty ediffs and
SQL like searches. Check it out!
... _Fish Eye for the Python CVS repository:
http://fisheye.cenqua.com/viewrep/python/
Contributing Threads:
- `FishEye on Python CVS Repository
<http://mail.python.org/pipermail/python-dev/2005-June/054127.html>`__
[SJB]
--------------------------------
PyPy Sprint: July 1st - 7th 2005
--------------------------------
The next `PyPy`_ sprint is scheduled right after EuroPython 2005 in
Gothenborg, Sweden. It will focus mainly on translating P...
python-dev Summary for 2006-05-01 through 2006-05-15python-dev Summary for 2006-05-01 through 2006-05-15
++++++++++++++++++++++++++++++++++++++++++++++++++++
... contents::
[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2006-05-01_2006-05-15]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Announcements
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
-------------------
Python 2.5 progress
-------------------
Python 2.5 is moving steadily towards its first beta release. See
`PEP 356`_ for more details and the full schedule.
... _PEP 356: http://www.python.org/dev/peps/pep-0356/
Contributing threads:
- `2.5 open i...
python-dev Summary for 2005-01-16 through 2005-01-31=====================
Summary Announcements
=====================
-----------------------------------------
School sure likes to destroy my free time
-----------------------------------------
A month late, that much closer to having this hectic quarter being over. Sorry
for being so delinquent with this summary but school has kept me busy and
obviously the Real World has to take precedence over volunteer work. Now if I
could only get paid for doing this... =)
And if you hate the summaries being late, you could do it yourself. This is
not meant to be a flippant comment! I am always w...
python-dev Summary for 2005-01-16 through 2005-01-31=====================
Summary Announcements
=====================
-----------------------------------------
School sure likes to destroy my free time
-----------------------------------------
A month late, that much closer to having this hectic quarter being over. Sorry
for being so delinquent with this summary but school has kept me busy and
obviously the Real World has to take precedence over volunteer work. Now if I
could only get paid for doing this... =)
And if you hate the summaries being late, you could do it yourself. This is
not meant to be a flippant comment! I am always willing to hand over
development of the summaries to anyone who is willing to do a comparable job.
If you are interested feel free to email me. I have now made this a permanent
offer in the header in case someone comes along later and decides they want to
do this.
----------------------
RSS feed now available
----------------------
Thanks entirely to one of my predecessors, A.M. Kuchling, the python-dev
Summaries are available as an `RSS feed`_. The feed contains the titles of
every summary and so will be updated with the newest summaries as soon as they
are posted online. A full text feed will eventually be available.
----------
New format
----------
I have done a thorough restructuring of the boilerplate and the Summary
Announcements section for the Summaries. The purpose of this is to make
finding information in the boilerplate mu...
python-dev Summary for 2005-02-01 through 2005-02-14[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-02-01_2005-02-14.html]
=====================
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
over.
The joy of ...
python-dev Summary for 2005-02-01 through 2005-02-14[The HTML version of this Summary is available at
http://www.python.org/dev/summary/2005-02-01_2005-02-14.html]
=====================
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
over.
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 for picking up where I left off. There is the possibility that they
will actually write the Summaries together as a team.
As for my last Summary,...