f



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 PyPy to lower leve=
l
backends, so as to move away from running PyPy on top of the CPython
interpreter.  There will be newcomer-friendly introductions, and other
topics are possible, so if you have any interest in PyPy,  now is the time
to help out!

... _PyPy: http://codespeak.net/pypy

Contributing Threads:

- `Post-EuroPython 2005 PyPy Sprint 1st - 7th July 2005
<http://mail.python.org/pipermail/python-dev/2005-
June/054162.html>`__

[SJB]


---------------------------------
Reminder: Google's Summer of Code
---------------------------------

Just a reminder that the friendly folks at Python have set up a `wiki`_ and
a `mailing list`_ for questions about  `Google's Summer of Code`_. For
specific details on particular projects (e.g. what needs done to complete
Python SSL  support) participants may also ask questions to the Python-Dev
list.

... _wiki: http://wiki.python.org/moin/CodingProjectIdeas
... _mailing list: http://mail.python.org/mailman/listinfo/summerofcode
... _Google's Summer of Code: http://code.google.com/summerofcode.html

[SJB]


----------------------
hashlib Review Request
----------------------
   =20

Gregory P. Smith noted that he has finished up the hashlib work he started
on a few months ago for patches `935454`_  and `1121611`_ (where the final
patch is).  He feels that the patch is ready, and would like anyone
interested to  review it; the patch incorporates both OpenSSL hash support
and SHA256+SHA512 support in a single module.  `The  documentation`_ can be
accessed separately, for convenience.


... _935454: http://python.org/sf/935454
... _1121611: http://python.org/sf/1121611
... _The documentation:
http://electricrain.com/greg/hashlib-py25-doc/module-hashlib.html

Contributing Threads:

- `hashlib - faster md5/sha, adds sha256/512 support
<http://mail.python.org/pipermail/python-dev/2005-
June/054156.html>`__

[TAM]

=3D=3D=3D=3D=3D=3D=3D=3D=3D
Summaries
=3D=3D=3D=3D=3D=3D=3D=3D=3D

----------------
PEP 343 Progress
----------------

The PEP 343 discussions were mostly concluded. Guido posted the newest
version of the PEP to both Python-Dev and  Python-List and the discussions
that followed were brief and mostly in agreement with the proposal.

The PEP 343 syntax was modified slightly to require parentheses if VAR is a
comma-separated list of variables.  This  made the proposal
forward-compatible to extending the with-block for multiple resources. In
the favored extension,  the with-block would take multiple expressions in a
manner analogous to import statements::

    with EXPR1 [as VAR1], EXPR2 [as VAR2], ...:
        BLOCK

However, if this extension becomes part of Python, it will likely enter
some time after Python 2.5, once users have a better idea of what with-bloc=
k
use-cases look like.

There were also some brief discussions about how with-blocks should behave
in the presence of async exceptions like  the KeyboardInterrupt generated
from a ^C. While it seemed like it would be a nice property for with-blocks
to  guarantee that the __exit__ methods would still be called in the
presence of async exceptions, making such a  guarantee proved to be too
complicated.  Thus the final conclusion, as summarized by Nick Coghlan, was
that "with  statements won't make any more guarantees about this than
try/finally statements do".

Contributing Threads:

- `PEP 343 rewrite complete
<http://mail.python.org/pipermail/python-dev/2005-June/054039.html>`__

- `For review: PEP 343: Anonymous Block Redux and Generator
Enhancements <http://mail.python.org/pipermail/python-
dev/2005-June/054082.html>`__

- `PEP 343 - next steps
<http://mail.python.org/pipermail/python-dev/2005-June/054138.html>`__

- `PEP 343 question
<http://mail.python.org/pipermail/python-dev/2005-June/054230.html>`__

[SJB]


--------------
Do-While Loops
--------------

Raymond Hettinger asked for a "dowhile" loop of the form::

    dowhile <cond>:
        <body>

which would run <body> once before testing the <cond>, and then proceed as =
a
normal while-loop. He was subsequently  referred to `PEP 315`_, which
proposes a slightly different syntax for a similar purpose.

The discussion expanded to not only do-while loops, but also loops with
break conditions at locations other than the  beginning and the end of a
loop. A variety of syntax proposals were suggested, but none seemed
compellingly better  than the current syntax::

    while True:
        ...
        if <cond>:
            break
        ...

which supports putting the condition(s) at any location in the loop.

... _PEP 315: http://www.python.org/peps/pep-0315.html
       =20
Contributing Threads:

- `Wishlist: dowhile
<http://mail.python.org/pipermail/python-dev/2005-June/054167.html>`__

[SJB]


------------------------------------
Reference Counting in Module Globals
------------------------------------

Both Michael Hudson and Skip Montanaro noticed that Py_INCREFs appeared to
be unnecessary when adding an object to a  module's globals. Armin Rigo
explained that after a module is initialized, the import mechanism makes a
"hidden"  copy of the module's dict so that the module can be reloaded. Thi=
s
means that objects added as module globals will  always have an extra
reference count in this hidden dict.

However, Armin Rigo agreed with Michael Hudson that this explanation was no
longer applicable after an interpreter  shutdown. The best conclusion he
could draw in this a situation: "it's all quite obscure".

Contributing Threads:

- `refcounting vs PyModule_AddObject
<http://mail.python.org/pipermail/python-dev/2005-June/054232.html>`__
- `[Python-checkins] python/dist/src/Modules _csv.c, 1.37, 1.38
<http://mail.python.org/pipermail/python-dev/2005-
June/054239.html>`__

[SJB]

-----------------------------------------
Reorganising the standard library (again)
-----------------------------------------

The ever-popular topic of reorganising the standard library came up again
this fortnight, courtesy of Reinhold  Birkenfeld.  The questions posed
included hierarchy (flat/nested), third party modules, size (batteries
included or  not), and the standard GUI toolkit.

As usual, there was a great deal of discussion, but not a great deal of
consensus about any of these (other than  that including ElementTree in the
standard library would be good), and given the amount of breakage this woul=
d
involve (and that Guido didn't weigh in at all), it seems unlikely that muc=
h
will change before Python 3000;  although Josiah Carlson indicated that he
had a patch that would avoid a lot of breakage.
   =20
Contributing Threads:

- `Thoughts on stdlib evolvement
<http://mail.python.org/pipermail/python-dev/2005-June/054092.html>`__

[TAM]

--------------------------
First Mac-tel, now Py-tel?
--------------------------

Guido mentioned that Intel has a free (as in beer) C `compiler for Linux`_,
and that a friend of his (who is  involved in its production and marketing)
would like to see how it performs with Python.  The compiler wasn't news  t=
o
some of the -dev crowd, though, with Martin v. L=F6wis pointing out a `bug
report on the compiler`_, as well as a  `patch`_, and a `message indicating
that some people had problems`_ with the resulting interpreter.

Martin pointed out that there were some old (2002 and 2004) results
indicating that the Intel compiler was slightly  faster, but couldn't find
any results for the latest version.  Michael Hoffman gave summaries of more
testing, which  gave a 16% speed increase.  He felt that, while this was
significant, he wasted a lot of time dealing with resulting problems with
extension modules, and so it doesn't use as much any more.
   =20

... _compiler for Linux:
http://www.intel.com/software/products/compilers/clin/index.htm
... _bug report on the compiler: http://python.org/sf/1162001
... _patch: http://python.org/sf/1162023
... _message indicating that some people had problems:
http://mail.python.org/pipermail/python-list/2005-March/270672.html

Contributing Threads:

- `Compiling Python with Intel compiler?
<http://mail.python.org/pipermail/python-dev/2005-June/054227.html>`__

[TAM]

------------------
sys.path Behaviour
------------------

Reinhold Birkenfeld noticed that sys.path's first element is '' in
interactive sessions, but the directory  containing the script otherwise,
and wondered if this was intentional.  Guido clarified that he's always
liked it  this way, so that if you use os.path.join to join it with a scrip=
t
name you don't get a spurious ".\" preprended.

The "absolutizing" of sys.path entries, however, is reasonably new; Bob
Ippolito pointed out that is also  `problematic with regards to path
hooks`_.  He has a `patch to fix it`_, but hasn't had a chance to commit it=
;
Phillip J. Eby noted that the patch doesn't fix completely fix it, however,
and indicated that fixing site.py with  respect to `PEP 302`_ will be quite
challenging.
=20
... _problematic with regards to path hooks:
http://mail.python.org/pipermail/python-dev/2005-April/052885.html
... _patch to fix it: http://python.org/sf/1174614
... _PEP 302: http://python.org/peps/pep-0302.html

Contributing Threads:

- `sys.path in interactive session
<http://mail.python.org/pipermail/python-dev/2005-June/054077.html>`__

[TAM]

----------------
More on old bugs
----------------
   =20
The discussion about what to do with old bugs continued this fortnight.
Against the concern about prematurely  closing old bugs, there was the
suggestion that given that there are such a huge number of open bug reports=
,
and  since closed bugs can be reopened, this wasn't such a problem.  It was
suggested that the act of closing a bug might  trigger activity to get it
fixed, if necessary.  The thread died off before a consensus was reached,
unfortunately.


Contributing Threads:

- `Closing old bugs
<http://mail.python.org/pipermail/python-dev/2005-June/054038.html>`__

[TAM]

---------------------------------
Improved pseudo-switch statements
---------------------------------

Skip Montanaro has been playing around with getting the Python compiler to
recognize switch-like statements and  generate O(1) code out of them.  The
rules are that the object being compared ('x') can be any expression, but
must  be precisely the same in each elif clause, the comparison operator
must be "=3D=3D", and the right-hand-side of the test  must evaluate to a s=
imple
hashable constant.  However, if evaluating 'x' has side-effects, then this
would break  code.

Various people felt that it was unwise to allow 'x' to be any expression;
Anthony Baxter suggested that one could  allow any local object that didn't
define a comparison operator.
=20
Contributing Threads:

- `Multiple expression eval in compound if statement?
<http://mail.python.org/pipermail/python-dev/2005-
June/054164.html>`__

[TAM]

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Skipped Threads
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

- `Adventures with Decimal
<http://mail.python.org/pipermail/python-dev/2005-June/054046.html>`__

- `Weekly Python Patch/Bug Summary
<http://mail.python.org/pipermail/python-dev/2005-June/054049.html>`__

- `AST manipulation and source code generation
<http://mail.python.org/pipermail/python-dev/2005-
June/054052.html>`__

- `Vestigial code in threadmodule?
<http://mail.python.org/pipermail/python-dev/2005-June/054054.html>`__

- `[Python-checkins] python/dist/src/Lib sre_compile.py, 1.57, 1.58
<http://mail.python.org/pipermail/python-
dev/2005-June/054069.html>`__

- `Split MIME headers into multiple lines near a space
<http://mail.python.org/pipermail/python-dev/2005-
June/054090.html>`__

- `python running in several threads
<http://mail.python.org/pipermail/python-dev/2005-June/054110.html>`__

- `problem installing current cvs
<http://mail.python.org/pipermail/python-dev/2005-June/054116.html>`__

- `b32encode and NUL bytes
<http://mail.python.org/pipermail/python-dev/2005-June/054130.html>`__

- `Example workaround classes for using Unicode with csv module...
<http://mail.python.org/pipermail/python-
dev/2005-June/054129.html>`__

- `Weekly Python Patch/Bug Summary
<http://mail.python.org/pipermail/python-dev/2005-June/054128.html>`__

- `[Python-checkins] python/dist/src/Doc/lib libtokenize.tex, 1.5, 1.6
<http://mail.python.org/pipermail/python-
dev/2005-June/054131.html>`__

- `Five patch reviews & patch request
<http://mail.python.org/pipermail/python-dev/2005-June/054135.html>`__

- `AIX 4.3, Python 2.4.1 fails in test_exceptions with a core dump
<http://mail.python.org/pipermail/python-
dev/2005-June/054197.html>`__

- `PEP 342 - Enhanced Iterators
<http://mail.python.org/pipermail/python-dev/2005-June/054201.html>`__

- `A bug in pyconfig.h under Linux?
<http://mail.python.org/pipermail/python-dev/2005-June/054214.html>`__

- `Dynamic class inheritance && something else
<http://mail.python.org/pipermail/python-dev/2005-
June/054218.html>`__

- `Weekly Python Patch/Bug Summary
<http://mail.python.org/pipermail/python-dev/2005-June/054229.html>`__

=3D=3D=3D=3D=3D=3D=3D=3D
Epilogue
=3D=3D=3D=3D=3D=3D=3D=3D

------------
Introduction
------------

This is a summary of traffic on the `python-dev mailing list`_ from
June 01, 2005 through June 15, 2005.

It is intended to inform the wider Python community of on-going
developments on the list on a semi-monthly basis.  An archive_ of
previous summaries is available online.

An `RSS feed`_ of the titles of the summaries is available.  You can
also watch comp.lang.python or comp.lang.python.announce for new
summaries (or through their email gateways of python-list or
python-announce, respectively, as found at http://mail.python.org).

This is the fifth summary written by the python-dev summary cabal of
Steve Bethard, Tim Lesher, and Tony Meyer.

To contact us, please send email:

- Steve Bethard (steven.bethard at gmail.com)
- Tim Lesher (tlesher at gmail.com)
- Tony Meyer (tony.meyer at gmail.com)

Do *not* post to comp.lang.python if you wish to reach us.

The `Python Software Foundation`_ is the non-profit organization that
holds the intellectual property for Python.  It also tries to advance
the development and use of Python.  If you find the python-dev Summary
helpful please consider making a donation.  You can make a donation at
http://python.org/psf/donations.html .  Every penny helps so even a
small donation with a credit card, check, or by PayPal helps.


--------------------
Commenting on Topics
--------------------

To comment on anything mentioned here, just post to
`comp.lang.python`_ (or email python-list at 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`_!


-------------------------
How to Read the Summaries
-------------------------

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

Please note that this summary is written using reStructuredText_.  Any
unfamiliar punctuation is probably markup for reST_ (otherwise it is
probably regular expression syntax or a typo =3D); you can safely ignore
it.  I do suggest learning reST, though; it's simple and is accepted
for `PEP markup`_ and can be turned into many different formats like
HTML and LaTeX.  Unfortunately, even though reST is standardized, the
wonders of programs that like to reformat text do not allow me to
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`_.

... _python-dev: http://www.python.org/dev/
... _SourceForge: http://sourceforge.net/tracker/?group_id=3D5470
... _python-dev mailing list: http://mail.python.org/mailman/listinfo/python=
-dev
... _c.l.py:
... _comp.lang.python: http://groups.google.com/groups?q=3Dcomp.lang.python
... _PEP Markup: http://www.python.org/peps/pep-0012.html

... _Docutils: http://docutils.sf.net/
... _reST:
... _reStructuredText: http://docutils.sf.net/rst.html
... _PSF:
... _Python Software Foundation: http://python.org/psf/

... _last summary: http://www.python.org/dev/summary/
... _original text file:
http://www.python.org/dev/summary/2005-06-01_2005-06-15.ht
... _archive: http://www.python.org/dev/summary/
... _RSS feed: http://www.python.org/dev/summary/channews.rdf
0
Steven
6/25/2005 10:49:09 PM
comp.lang.python.announce 7374 articles. 0 followers. Post Follow

1 Replies
371 Views

Similar Articles

[PageSpeed] 59

Some basic helper functions to deal with encodings of files retrieved 
via HTTP.

	Download from http://cthedot.de/encutils/


Currently contained functions:

encodingByMediaType(media_type, log=None)
     Returns for the given Content-Type a default encoding if available, 	
     e.g. 'utf-8' for 'application/xml'.

getHTTPInfo(httpheaders, log=None)
     Finds content-type and encoding information from HTTP header
     dictionary. Returns (Content-Type, encoding) tuple which may be
     both None. Default encodings of specific Content-Types is used
     (see encodingByContentType).

getMetaInfo(text, log=None)
     Returns (Content-Type, encoding) tuple from (last) X/HTML meta
     element.

guessEncoding(httpheaders, text, log=None)
     Tries to find encoding of given text and uses information in
     httpheaders and textcontent like HTML meta elements or the XML
     declaration (this is not implemented yet). Returns the explicit
     or implicit encoding or None. Mismatch reports are written to the
     log.


If there is a similar thing out please let me know (I know the Cookbook 
XML autodetection script which I like to intregrate).

And I would very much appreciate any feedback about spec compliance, 
errors or other problems with the functions too. (See 
http://cthedot.de/contact/ or http://cthedot.de/blog/).

Thanks a lot!
chris
0
csad7
6/26/2005 7:58:30 PM
Reply:

Similar Artilces:

python-dev Summary for 2005-06-16 through 2005-06-30
[The HTML version of this Summary is available at http://www.python.org/dev/summary/2005-06-16_2005-06-30.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 ------------------ OSCON Registration ------------------ Though if you haven't yet registered, you've already missed the early registration period (which ended June 20), you should still consider taking a look at the O'Reilly Open Source Convention (OSCON). Guido assures us that "the Python program is really good!" Contributing Thread: - `Please spread the word about OSCON early reg deadline <http://mail.python.org/pipermail/python-dev/2005-June/054259.html>`__ =3D=3D=3D=3D=3D=3D=3D=3D=3D Summaries =3D=3D=3D=3D=3D=3D=3D=3D=3D ------------ PEP Clean Up ------------ Raymond Hettinger decided to go through the `list of PEPs`_ and do some spring cleaning (late for the Northern Hemisphere, but early down south). * Rejection of `PEP 303`_ ("Extend divmod() for Multiple Divisors") was proposed on the grounds that it has been open for two and half years and hasn't generated discussion or support, is unpersuasive, and unnecessary. No-one spoke up for it (and some against), so it is now rejected. * Rejection of `PEP 254`_ ("Making Classes Look More Like Types") was proposed on the grounds that it is only an empty stub and is un...

python-dev Summary for 2005-06-16 through 2005-06-30
[The HTML version of this Summary is available at http://www.python.org/dev/summary/2005-06-16_2005-06-30.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 ------------------ OSCON Registration ------------------ Though if you haven't yet registered, you've already missed the early registration period (which ended June 20), you should still consider taking a look at the O'Reilly Open Source Convention (OSCON). Guido assures us that "the Python program is really good!&qu...

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

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

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-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 2004-06-01 through 2004-06-15
python-dev Summary for 2004-06-01 through 2004-06-15 ++++++++++++++++++++++++++++++++++++++++++++++++++++ This is a summary of traffic on the `python-dev mailing list`_ from June 01, 2004 through June 15, 2004. 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 forty-third summary written by Brett Cannon (wonder if that summary count is correct?). 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...

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=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-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-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-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 2004-06-01 through 2004-06-15
python-dev Summary for 2004-06-01 through 2004-06-15 ++++++++++++++++++++++++++++++++++++++++++++++++++++ This is a summary of traffic on the `python-dev mailing list`_ from June 01, 2004 through June 15, 2004. 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'...

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-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-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-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-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-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-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-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 2003-06-01 through 2003-06-30
python-dev Summary for 2003-06-01 through 2003-06-30 ++++++++++++++++++++++++++++++++++++++++++++++++++++ This is a summary of traffic on the `python-dev mailing list`_ from June=20 1, 2003 through June 30, 2003. It is intended to inform the wider=20 Python community of on-going developments on the list and to have an=20 archived summary of each thread started on the list. To comment on=20 anything mentioned here, just post to python-list@python.org or=20 `comp.lang.python`_ with a subject line mentioning what you are=20 discussing. All python-dev members are interested in seeing ideas=20 di...

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

Resources last updated: 3/3/2016 9:39:59 PM