2011年2月22日

[installer 2698] Python-3.2

Python-3.2 出ています。

☆ Python-3.2
http://www.python.org/
http://www.python.org/download/releases/3.2/
http://www.python.org/ftp/python/3.2/Python-3.2.tgz

****************************

What's New In Python 3.2
****************************

:Author: Raymond Hettinger
:Release: |release|
:Date: |today|

.. $Id$
Rules for maintenance:

* Anyone can add text to this document. Do not spend very much time
on the wording of your changes, because your text will probably
get rewritten. (Note, during release candidate phase or just before
a beta release, please use the tracker instead -- this helps avoid
merge conflicts. If you must add a suggested entry directly,
please put it in an XXX comment and the maintainer will take notice).

* The maintainer will go through Misc/NEWS periodically and add
changes; it's therefore more important to add your changes to
Misc/NEWS than to this file.

* This is not a complete list of every single change; completeness
is the purpose of Misc/NEWS. Some changes I consider too small
or esoteric to include. If such a change is added to the text,
I'll just remove it. (This is another reason you shouldn't spend
too much time on writing your addition.)

* If you want to draw your new text to the attention of the
maintainer, add 'XXX' to the beginning of the paragraph or
section.

* It's OK to just add a fragmentary note about a change. For
example: "XXX Describe the transmogrify() function added to the
socket module." The maintainer will research the change and
write the necessary text.

* You can comment out your additions if you like, but it's not
necessary (especially when a final release is some months away).

* Credit the author of a patch or bugfix. Just the name is
sufficient; the e-mail address isn't necessary. It's helpful to
add the issue number:

XXX Describe the transmogrify() function added to the socket
module.

(Contributed by P.Y. Developer; :issue:`12345`.)

This saves the maintainer the effort of going through the SVN log
when researching a change.

This article explains the new features in Python 3.2 as compared to 3.1. It
focuses on a few highlights and gives a few examples. For full details, see the
:source:`Misc/NEWS <Misc/NEWS>` file.

.. seealso::

:pep:`392` - Python 3.2 Release Schedule


PEP 384: Defining a Stable ABI
==============================

In the past, extension modules built for one Python version were often
not usable with other Python versions. Particularly on Windows, every
feature release of Python required rebuilding all extension modules that
one wanted to use. This requirement was the result of the free access to
Python interpreter internals that extension modules could use.

With Python 3.2, an alternative approach becomes available: extension
modules which restrict themselves to a limited API (by defining
Py_LIMITED_API) cannot use many of the internals, but are constrained
to a set of API functions that are promised to be stable for several
releases. As a consequence, extension modules built for 3.2 in that
mode will also work with 3.3, 3.4, and so on. Extension modules that
make use of details of memory structures can still be built, but will
need to be recompiled for every feature release.

.. seealso::

:pep:`384` - Defining a Stable ABI

投稿者 xml-rpc : 2011年2月22日 09:51
役に立ちました?:
過去のフィードバック 平均:(0) 総合:(0) 投票回数:(0)
本記事へのTrackback: http://hoop.euqset.org/blog/mt-tb2006.cgi/102213
トラックバック
コメント
コメントする




画像の中に見える文字を入力してください。