f



python-dev Summary for 2005-01-01 through 2005-01-15

This 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 summary 
through Docutils_ as-is unless it is from the `original text file`_.

... _PEP Markup: http://www.python.org/peps/pep-0012.html

The in-development version of the documentation for Python can be found at
http://www.python.org/dev/doc/devel/ and should be used when looking up any
documentation on new code; otherwise use the current documentation as found at
http://docs.python.org/ .  PEPs (Python Enhancement Proposals) are located at 
http://www.python.org/peps/ .  To view files in the Python CVS online, go to 
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python/ .  Reported bugs and 
suggested patches can be found at the SourceForge_ project page.

The `Python Software Foundation`_ is the non-profit organization that holds the 
intellectual property for Python.  It also tries to forward the development and 
use of Python.  But the PSF_ cannot do this without donations.  You can make a 
donation at http://python.org/psf/donations.html .  Every penny helps so even a 
small donation (you can donate through PayPal or by check) helps.

... _python-dev: http://www.python.org/dev/
... _SourceForge: http://sourceforge.net/tracker/?group_id=5470
... _python-dev mailing list: http://mail.python.org/mailman/listinfo/python-dev
... _comp.lang.python: http://groups.google.com/groups?q=comp.lang.python
... _Docutils: http://docutils.sf.net/
... _reST:
... _reStructuredText: http://docutils.sf.net/rst.html
... _PSF:
... _Python Software Foundation: http://python.org/psf/

... contents::

... _last summary: http://www.python.org/dev/summary/2004-12-16_2004-12-31.html
... _original text file: http://www.python.org/dev/summary/2005-01-01_2005-01-15.ht



=====================
Summary Announcements
=====================
PyCon_ will be upon us come late March!  Still time to plan to go.

A warning on the thoroughness off this summary is in order.  While trying to 
delete a single thread of email I managed to accidentally delete my entire 
python-dev mailbox.  I did the best I could to retrieve the emails but it's 
possible I didn't resuscitate all of my emails, so I may have overlooked something.

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

=======
Summary
=======
-------------
PEP movements
-------------
tip:: PEP updates by email are available as a topic from the `Python-checkins`_ 
mailing list.

`PEP 246`_ was a major topic of discussion during the time period covered by 
this summary.  This all stemmed from `Guido's blog`_ entries on optional type 
checking. This led to a huge discussion on many aspects of protocols, 
interfaces, and adaptation and the broadening of this author's vocabulary to 
include "Liskov violation".

"Monkey typing" also became a new term to know thanks to Phillip J. Eby's 
proto-PEP on the topic (found at 
http://peak.telecommunity.com/DevCenter/MonkeyTyping).  Stemming from the 
phrase "monkey see, monkey do", it's Phillip version of taking PEP 246 
logically farther (I think; the whole thing is more than my currently 
burned-out-on-school brain can handle right now).

... _Python-checkins: http://mail.python.org/mailman/listinfo/python-checkins
... _PEP 246: http://www.python.org/peps/pep-0246.html
... _Guido's blog: http://www.artima.com/weblogs/index.jsp?blogger=guido

Contributing threads:
   - `getattr and __mro__ 
<http://mail.python.org/pipermail/python-dev/2005-January/050907.html>`__
   - `Son of PEP 246, redux 
<http://mail.python.org/pipermail/python-dev/2005-January/050972.html>`__
   - `PEP 246: lossless and stateless 
<http://mail.python.org/pipermail/python-dev/2005-January/051023.html>`__
   - `PEP 246: LiskovViolation as a name 
<http://mail.python.org/pipermail/python-dev/2005-January/050878.html>`__
   - `"Monkey Typing" pre-PEP, partial draft 
<http://mail.python.org/pipermail/python-dev/2005-January/051124.html>`__


------------------------------------------------------------------------------------
Optional type checking: how to inadvertently cause a flame war worse than 
decorators
------------------------------------------------------------------------------------
`Guido's blog`_ had comments on the idea of adding optional static type 
checking to Python.  While just comments in a blog, it caused a massive 
response from people, mostly negative from what I gathered.  After Guido 
discussed things some more it culminated in a blog entry found at 
http://www.artima.com/weblogs/viewpost.jsp?thread=87182 that lays out what his 
actual plans are.  I highly recommend reading it since it suggests adding 
optional run-time type checking for function arguments along with some other 
proposals.

All of this led to `PEP 246`_ getting updated.  For some more details on that 
see the `PEP movements`_ section of this summary.

And if there is a lesson to be learned from all of this, it's that when Alex 
Martelli and Phillip J. Eby start a technical discussion it's going to be long, 
in-depth, complex, and lead to my inbox being brimming in python-dev email.


------------------------------
Let's get the AST branch done!
------------------------------
Guido posted an email to the list stating he would like to to make progress 
towards integrating "things like type inferencing, integrating PyChecker, or 
optional static type checking" into Python.  In order to make that easier he 
put out a request that people work on the AST branch and finish it.

For those that don't know about Python's back-end, the compiler as it stands 
now takes the parse tree from the parser and emits bytecode directly from that. 
  This is far from optimal since the parse tree is more verbose than needed and 
it is not the easiest thing to work with.

The AST branch attempts to fix this by taking a more traditional approach to 
compiling.  This means the parse tree is used to generate an AST (abstract 
syntax tree; and even more technically could be considered a control flow graph 
in view of how it is implemented) which in turn is used to emit bytecode.  The 
AST itself is much easier to work with when compared to the parse tree; better 
to know you are working with an 'if' guard thanks to it being an 'if' node in 
the AST than checking if the parse tree statement you are working with starts 
with 'if' and ends with a ':'.

While all of this sounds great, the issue is the AST branch is not finished 
yet.  It is not entirely far off, but new features from 2.4 (decorators and 
generator expressions) need to be added along with more bug fixing and clean up.

This means the AST branch is going to get finished for 2.5 somehow.  But help 
is needed.  While the usual suspects who have previously contributed to the 
branch are hoping to finish it, more help is always appreciated.  If you care 
to get involved, check out the AST branch (tagged as 'ast-branch' in CVS; see 
the `python-dev FAQ`_ on how to do a tagged branch checkout), read 
Python/compile.txt and just dive in!  There will also be a sprint on the AST 
branch at PyCon.

... _python-dev FAQ: http://www.python.org/dev/devfaq.html

Contributing threads:
   - `Please help complete the AST branch 
<http://mail.python.org/pipermail/python-dev/2005-January/050606.html>`__
   - `Will ASTbranch compile on windows yet? 
<http://mail.python.org/pipermail/python-dev/2005-January/050633.html>`__
   - `ast branch pragmatics 
<http://mail.python.org/pipermail/python-dev/2005-January/050690.html>`__
   - `Re: [Python-checkins] python/dist/src/Python pythonrun.c, 2.161.2.15, 
2.161.2.16 
<http://mail.python.org/pipermail/python-dev/2005-January/050786.html>`__


--------------------------------
Ditching unbound methods in Py3k
--------------------------------
Guido suggested removing unbound methods from Python since their usefulness of 
checking their first argument and other slight differences from functions just 
didn't seem worth keeping around and complicating the language.  So the idea 
seems sound.

But then people with uses for the extra information kept in unbound methods 
(im_func and im_self) popped up.  To make the long thread short, enough people 
stepped up mentioning uses they had for the information for Guido to retract 
the suggestion in the name of backwards compatibility.

But unbound methods are now on the list of things to go in Python 3000.

Contributing threads:
   - `Let's get rid of unbound methods 
<http://mail.python.org/pipermail/python-dev/2005-January/050625.html>`__
   - `Getting rid of unbound methods: patch available 
<http://mail.python.org/pipermail/python-dev/2005-January/051128.html>`__
   - `PEP 246 - concrete assistance to developers of new	adapter classes 
<http://mail.python.org/pipermail/python-dev/2005-January/051246.html>`__


------------------------------------------
Getting exceptions to be new-style classes
------------------------------------------
A patch to allow exceptions to be new-style classes is currently at 
http://www.python.org/1104669 .  The plan is to get that patch in order, apply 
it, and as long as a ton of code does not break from exceptions moving from 
classic to new-style classes it will be made permanent in 2.5 .

This in no way touches on the major changes as touched upon in a `previous 
summary 
<http://www.python.org/dev/summary/2004-09-01_2004-09-15.html#cleaning-the-exception-house>`__ 
which will need a PEP to get the hierarchy cleaned up and discuss any possible 
changes to bar 'except' statements.

Contributing threads:
   - `Exceptions *must*? be old-style classes? 
<http://mail.python.org/pipermail/python-dev/2005-January/051097.html>`__

-----------------------------
Recent IBM patents and Python
-----------------------------
note:: contributed by Jim Jewett

Current python policy is that all submissions must be unemcumbered
by intellectual property claims.  See 
http://www.python.org/psf/psf-contributor-agreement.html

IBM has recently released several patents for use in Open Source
Software, with the restriction that they can revoke the grant if you
sue to enforce any Intellectual Property rights against any Open
Source project.

Is this an acceptable license restriction, or should code covered by
these patents be rejected?  No explicit decision was made.

Contributing threads:
   - `Recent IBM Patent releases 
<http://mail.python.org/pipermail/python-dev/2005-January/050919.html>`__

===============
Skipped Threads
===============
- Mac questions
- 2.3.5 schedule, and something I'd like to get in
-  csv module TODO list
- an idea for improving struct.unpack api
- Minor change to behaviour of csv module
- PATCH/RFC for AF_NETLINK support
- logging class submission
- frame.f_locals is writable
- redux: fractional seconds in strptime
- Darwin's realloc(...) implementation never shrinks allocations
0
Brett
2/7/2005 11:35:45 PM
comp.lang.python.announce 7374 articles. 0 followers. Post Follow

0 Replies
469 Views

Similar Articles

[PageSpeed] 37

Reply:

Similar Artilces:

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-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 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 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-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-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-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-05-01 through 2005-05-15
[The HTML version of this Summary is available at http://www.python.org/dev/summary/2005-05-01_2005-05-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 ---------------------------------------------- PEP 340 Episode 2: Revenge of the With (Block) ---------------------------------------------- This fornight's Python-Dev was dominated again by another nearly 400 messages on the topic of anonymous block statements. The discussion was a little more focused than the last thanks mainly to Guido's introduction of `PEP 340`_. Discussion of this PEP resulted in a series of other PEPs, including * `PEP 342`_: Enhanced Iterators, which broke out into a separate PEP the parts of `PEP 340`_ that allowed code to pass values into iterators using ``continue EXPR`` and yield-expressions. * `PEP 343`_: Anonymous Block Redux, a dramatically simplified version of `PEP 340`_, which removed the looping nature of the anonymous blocks and the injection-of-exceptions semantics for generators. * `PEP 3XX`_: User Defined ("with") Statements, which proposed non-looping anonymous blocks accompanied by finalization semantics for iterators and generators in for loops. Various details of each of these proposals are discussed below in the sections: 1. `Enhanced Iterators`_ 2. `Separate APIs for Iterators and Anonymous Blocks`_...

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-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-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-05-01 through 2005-05-15
[The HTML version of this Summary is available at http://www.python.org/dev/summary/2005-05-01_2005-05-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 ---------------------------------------------- PEP 340 Episode 2: Revenge of the With (Block) ---------------------------------------------- This fornight's Python-Dev was dominated again by another nearly 400 messages on the topic of anonymous block statements. The discussion was a little more focused than the last thanks mainly...

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-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-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 2006-01-01 through 2006-01-15
[The HTML version of this Summary is available at http://www.python.org/dev/summary/2006-01-01_2006-01-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 ---------------------------- Guido, on the crashability of Python: I'm not saying it's uncrashable. I'm saying that if you crash it, it's a bug unless proven harebrained. Contributing thread: - `Include ctypes into core Python? <http://mail.python.org/pipermail/python-dev/2006-January/059621.html>`_ [SJB] ------------------------------------ Brett Cannon looking for Ph.D. ideas ------------------------------------ Brett Cannon is looking for Python-related ideas to form the subject of his PhD dissertation, under Eric Wohlstadter at the University of British Columbia. He has three areas in which he has possible funding (XML integration, game scripting support, and AOP); he is open to grants from anyone else interested in particular Python development.=20 If anyone has suggestions for topics, Brett is listening! So far: * Phillip J. Eby mentioned that he has been doing some research on implementing a non-traditional form of AOP in Python. * Bill Janssen suggested a system to compile Python to AJAX. * Steve Holden suggested a Python learning system. * Ian Bicking suggested Boxer_ implemented for Python. * Armin Rigo suggested PyPy related w...

python-dev Summary for 2006-01-01 through 2006-01-15
[The HTML version of this Summary is available at http://www.python.org/dev/summary/2006-01-01_2006-01-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 ---------------------------- Guido, on the crashability of Python: I'm not saying it's uncrashable. I'm saying that if you crash it, it's a bug unless proven harebrained. Contributing thread: - `Include ctypes into core Python? <http://mail.python.org/pipermail/python-dev/2006-January/059621.html>`_ [...

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,...

python-dev Summary for 2004-01-01 through 2004-01-31
python-dev Summary for 2004-01-01 through 2004-01-31 ++++++++++++++++++++++++++++++++++++++++++++++++++++ This is a summary of traffic on the `python-dev mailing list`_ from=20 January 1, 2004 through January 31, 2004. It is intended to inform the=20 wider Python community of on-going developments on the list. To comment=20 on anything mentioned here, just post to `comp.lang.python`_ (or email=20 python-list@python.org which is a gateway to the newsgroup) with a=20 subject line mentioning what you are discussing. All python-dev members=20 are interested in seeing ideas discussed by the community, so don't=20 hesitate to take a stance on something. And if all of this really=20 interests you then get involved and join `python-dev`_! This is the thirty-third and -fourth summaries written by Brett Cannon=20 (who is rather fed up with being sick recently). To contact me, please send email to brett at python.org ; I do not have=20 the time to keep up on comp.lang.python and thus do not always catch=20 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=20 can be found at http://docutils.sf.net/rst.html . Any unfamiliar=20 punctuation is probably markup for reST_ (otherwise it is probably=20 regular expression syntax or a typo =3D); you can safely ignore it,=20 although I suggest learning reST; it's simple and is accepted for `PEP=20...

python-dev Summary for 2004-01-01 through 2004-01-31
python-dev Summary for 2004-01-01 through 2004-01-31 ++++++++++++++++++++++++++++++++++++++++++++++++++++ This is a summary of traffic on the `python-dev mailing list`_ from=20 January 1, 2004 through January 31, 2004. It is intended to inform the=20 wider Python community of on-going developments on the list. To comment=20 on anything mentioned here, just post to `comp.lang.python`_ (or email=20 python-list@python.org which is a gateway to the newsgroup) with a=20 subject line mentioning what you are discussing. All python-dev members=20 are interested in seeing ideas discussed by the commu...

Web resources about - python-dev Summary for 2005-01-01 through 2005-01-15 - comp.lang.python.announce

Resources last updated: 3/3/2016 10:11:22 PM