Skip to content

C
cpython
Commit 5a165584 authored by Georg Brandl's avatar Georg Brandl
Browse files
Options

Correct a few typos.

parent 64fd6fb2
Show whitespace changes
Inline Side-by-side
Showing with 75 additions and 76 deletions
Doc/whatsnew/3.0.rst
View file @ 5a165584
...@@ -3,50 +3,48 @@ ...@@ -3,50 +3,48 @@
**************************** ****************************
:Author: A.M. Kuchling, Guido van Rossum :Author: A.M. Kuchling, Guido van Rossum
:Release: 0.1
.. |release| replace:: 0.0 .. Rules for maintenance:
.. % $Id: whatsnew26.tex 55506 2007-05-22 07:43:29Z neal.norwitz $ * Anyone can add text to this document. Do not spend very much time
.. % Rules for maintenance: on the wording of your changes, because your text will probably
.. % get rewritten to some degree.
.. % * Anyone can add text to this document. Do not spend very much time
.. % on the wording of your changes, because your text will probably * The maintainer will go through Misc/NEWS periodically and add
.. % get rewritten to some degree. changes; it's therefore more important to add your changes to
.. % Misc/NEWS than to this file.
.. % * The maintainer will go through Misc/NEWS periodically and add
.. % changes; it's therefore more important to add your changes to * This is not a complete list of every single change; completeness
.. % Misc/NEWS than to this file. 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,
.. % * This is not a complete list of every single change; completeness I'll just remove it. (This is another reason you shouldn't spend
.. % is the purpose of Misc/NEWS. Some changes I consider too small too much time on writing your addition.)
.. % 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 * If you want to draw your new text to the attention of the
.. % too much time on writing your addition.) maintainer, add 'XXX' to the beginning of the paragraph or
.. % section.
.. % * If you want to draw your new text to the attention of the
.. % maintainer, add 'XXX' to the beginning of the paragraph or * It's OK to just add a fragmentary note about a change. For
.. % section. example: "XXX Describe the transmogrify() function added to the
.. % socket module." The maintainer will research the change and
.. % * It's OK to just add a fragmentary note about a change. For write the necessary text.
.. % example: "XXX Describe the transmogrify() function added to the
.. % socket module." The maintainer will research the change and * You can comment out your additions if you like, but it's not
.. % write the necessary text. necessary (especially when a final release is some months away).
.. %
.. % * You can comment out your additions if you like, but it's not * Credit the author of a patch or bugfix. Just the name is
.. % necessary (especially when a final release is some months away). sufficient; the e-mail address isn't necessary.
.. %
.. % * Credit the author of a patch or bugfix. Just the name is * It's helpful to add the bug/patch number as a comment:
.. % sufficient; the e-mail address isn't necessary.
.. % % Patch 12345
.. % * It's helpful to add the bug/patch number as a comment: XXX Describe the transmogrify() function added to the socket
.. % module.
.. % % Patch 12345 (Contributed by P.Y. Developer.)
.. % XXX Describe the transmogrify() function added to the socket
.. % module. This saves the maintainer the effort of going through the SVN log
.. % (Contributed by P.Y. Developer.) when researching a change.
.. %
.. % 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.0, comparing to 2.6 This article explains the new features in Python 3.0, comparing to 2.6
(or in some cases 2.5, since 2.6 isn't released yet). (or in some cases 2.5, since 2.6 isn't released yet).
...@@ -59,15 +57,15 @@ full details, you should refer to the documentation for Python 3.0. If ...@@ -59,15 +57,15 @@ full details, you should refer to the documentation for Python 3.0. If
you want to understand the complete implementation and design you want to understand the complete implementation and design
rationale, refer to the PEP for a particular new feature. rationale, refer to the PEP for a particular new feature.
.. % Compare with previous release in 2 - 3 sentences here. .. Compare with previous release in 2 - 3 sentences here.
.. % add hyperlink when the documentation becomes available online. .. add hyperlink when the documentation becomes available online.
.. % ====================================================================== .. ======================================================================
.. % Large, PEP-level features and changes should be described here. .. Large, PEP-level features and changes should be described here.
.. % Should there be a new section here for 3k migration? .. Should there be a new section here for 3k migration?
.. % Or perhaps a more general section describing module changes/deprecation? .. Or perhaps a more general section describing module changes/deprecation?
.. % sets module deprecated .. sets module deprecated
.. % ====================================================================== .. ======================================================================
Common Stumbling Blocks Common Stumbling Blocks
...@@ -128,7 +126,7 @@ changes to rarely used features.) ...@@ -128,7 +126,7 @@ changes to rarely used features.)
Strings and Bytes Strings and Bytes
================= =================
* There is only on string type; its name is ``str`` but its behavior * There is only one string type; its name is ``str`` but its behavior
and implementation are more like ``unicode`` in 2.x. and implementation are more like ``unicode`` in 2.x.
* PEP 358: There is a new type, ``bytes``, to represent binary data * PEP 358: There is a new type, ``bytes``, to represent binary data
...@@ -177,12 +175,12 @@ Exception Stuff ...@@ -177,12 +175,12 @@ Exception Stuff
=============== ===============
* PEP 352: Exceptions must derive from BaseException. This is the * PEP 352: Exceptions must derive from BaseException. This is the
root of the exception hierarchy; only Exception, root of the exception hierarchy.
* StandardException was removed (already in 2.6). * StandardException was removed (already in 2.6).
* Dropping sequence behavior and ``.message`` attribute of exception * Dropping sequence behavior (slicing!) and ``.message`` attribute of
instances. exception instances.
* PEP 3109: Raising exceptions. You must now use ``raise * PEP 3109: Raising exceptions. You must now use ``raise
Exception(args)`` instead of ``raise Exception, args``. Exception(args)`` instead of ``raise Exception, args``.
...@@ -232,13 +230,13 @@ language and built-in functions. ...@@ -232,13 +230,13 @@ language and built-in functions.
* ``__getslice__()`` and friends killed. The syntax ``a[i:j]`` now * ``__getslice__()`` and friends killed. The syntax ``a[i:j]`` now
translates to ``a.__getitem__(slice(i, j))`` (or ``__setitem__`` translates to ``a.__getitem__(slice(i, j))`` (or ``__setitem__``
or ``__delitem``, depending on context). or ``__delitem__``, depending on context).
* PEP 3102: Keyword-only arguments. Named parameters occurring after * PEP 3102: Keyword-only arguments. Named parameters occurring after
``*args`` in the parameter list *must* be specified using keyword ``*args`` in the parameter list *must* be specified using keyword
syntax in the call. You can also use ``*`` in the parameter list to syntax in the call. You can also use a bare ``*`` in the parameter
indicate that you don't accept a variable-length argument list, but list to indicate that you don't accept a variable-length argument
you do have keyword-only arguments. list, but you do have keyword-only arguments.
* PEP 3104: ``nonlocal`` statement. Using ``nonlocal x`` you can now * PEP 3104: ``nonlocal`` statement. Using ``nonlocal x`` you can now
assign directly to a variable in an outer (but non-global) scope. assign directly to a variable in an outer (but non-global) scope.
...@@ -259,16 +257,17 @@ language and built-in functions. ...@@ -259,16 +257,17 @@ language and built-in functions.
``def foo(a, (b, c)): ...``. Use ``def foo(a, b_c): b, c = b_c`` ``def foo(a, (b, c)): ...``. Use ``def foo(a, b_c): b, c = b_c``
instead. instead.
* PEP 3114: ``.next()`` renamed to ``.__next__()``. * PEP 3114: ``.next()`` renamed to ``.__next__()``, new builtin
``next()`` to call the ``__next__()`` method on an object.
* PEP 3127: New octal literals; binary literals and ``bin()``. * PEP 3127: New octal literals; binary literals and ``bin()``.
Instead of ``0666``, you write ``0o666``. The oct() function is Instead of ``0666``, you write ``0o666``. The oct() function is
modified accordingly. Also, ``0b1010`` equals 10, and ``bin(10)`` modified accordingly. Also, ``0b1010`` equals 10, and ``bin(10)``
returns ``"0b1010"``. returns ``"0b1010"``. ``0666`` is now a ``SyntaxError``.
* PEP 3132: Extended Iterable Unpacking. You can now write things * PEP 3132: Extended Iterable Unpacking. You can now write things
like ``a, b, *rest = some_sequence``. And even ``*rest, a = like ``a, b, *rest = some_sequence``. And even ``*rest, a =
stuff``. The ``rest`` variable is always a list; the right-hand stuff``. The ``rest`` object is always a list; the right-hand
side may be any iterable. side may be any iterable.
* PEP 3135: New ``super()``. You can now invoke ``super()`` without * PEP 3135: New ``super()``. You can now invoke ``super()`` without
...@@ -281,15 +280,15 @@ language and built-in functions. ...@@ -281,15 +280,15 @@ language and built-in functions.
``.uppercase``) are gone. Use ``string.ascii_letters`` ``.uppercase``) are gone. Use ``string.ascii_letters``
etc. instead. etc. instead.
* Removed: apply(), callable(), coerce(), execfile(), file(), * Removed: ``apply()``, ``callable()``, ``coerce()``, ``execfile()``,
reduce(), reload(). ``file()``, ``reduce()``, ``reload()``.
* Removed: ``dict.has_key()``. * Removed: ``dict.has_key()``.
* ``exec`` is now a function. * ``exec`` is now a function.
.. % ====================================================================== .. ======================================================================
Optimizations Optimizations
...@@ -301,7 +300,7 @@ The net result of the 3.0 generalizations is that Python 3.0 runs the ...@@ -301,7 +300,7 @@ The net result of the 3.0 generalizations is that Python 3.0 runs the
pystone benchmark around 25% slower than Python 2.5. There's room for pystone benchmark around 25% slower than Python 2.5. There's room for
improvement! improvement!
.. % ====================================================================== .. ======================================================================
New, Improved, and Deprecated Modules New, Improved, and Deprecated Modules
...@@ -316,10 +315,10 @@ through the CVS logs for all the details. ...@@ -316,10 +315,10 @@ through the CVS logs for all the details.
* The ``cPickle`` module is gone. Use ``pickle`` instead. Eventually * The ``cPickle`` module is gone. Use ``pickle`` instead. Eventually
we'll have a transparent accelerator module. we'll have a transparent accelerator module.
.. % ====================================================================== .. ======================================================================
.. % whole new modules get described in \subsections here .. whole new modules get described in subsections here
.. % ====================================================================== .. ======================================================================
Build and C API Changes Build and C API Changes
...@@ -331,9 +330,9 @@ Changes to Python's build process and to the C API include: ...@@ -331,9 +330,9 @@ Changes to Python's build process and to the C API include:
* PEP 3121: Extension Module Initialization & Finalization. * PEP 3121: Extension Module Initialization & Finalization.
* PEP 3123: Making PyObject_HEAD conform to standard C. * PEP 3123: Making ``PyObject_HEAD`` conform to standard C.
.. % ====================================================================== .. ======================================================================
Port-Specific Changes Port-Specific Changes
...@@ -341,7 +340,7 @@ Port-Specific Changes ...@@ -341,7 +340,7 @@ Port-Specific Changes
Platform-specific changes go here. Platform-specific changes go here.
.. % ====================================================================== .. ======================================================================
.. _section-other: .. _section-other:
...@@ -358,7 +357,7 @@ Some of the more notable changes are: ...@@ -358,7 +357,7 @@ Some of the more notable changes are:
* Details go here. * Details go here.
.. % ====================================================================== .. ======================================================================
Porting to Python 3.0 Porting to Python 3.0
...@@ -369,7 +368,7 @@ changes to your code: ...@@ -369,7 +368,7 @@ changes to your code:
* Everything is all in the details! * Everything is all in the details!
.. % ====================================================================== .. ======================================================================
.. _acks: .. _acks:
...@@ -379,5 +378,5 @@ Acknowledgements ...@@ -379,5 +378,5 @@ Acknowledgements
The author would like to thank the following people for offering The author would like to thank the following people for offering
suggestions, corrections and assistance with various drafts of this suggestions, corrections and assistance with various drafts of this
article: . article: Georg Brandl.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7