Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 5a16558

Browse files
birkenfeldbirkenfeld
committed
Correct a few typos.
1 parent 64fd6fb commit 5a16558

1 file changed

Lines changed: 75 additions & 76 deletions

File tree

‎Doc/whatsnew/3.0.rst‎

Lines changed: 75 additions & 76 deletions
Original file line numberDiff line numberDiff line change
@@ -3,50 +3,48 @@
33
****************************
44

55
:Author: A.M. Kuchling, Guido van Rossum
6-
7-
.. |release| replace:: 0.0
8-
9-
.. % $Id: whatsnew26.tex 55506 2007-05-22 07:43:29Z neal.norwitz $
10-
.. % Rules for maintenance:
11-
.. %
12-
.. % * Anyone can add text to this document. Do not spend very much time
13-
.. % on the wording of your changes, because your text will probably
14-
.. % get rewritten to some degree.
15-
.. %
16-
.. % * The maintainer will go through Misc/NEWS periodically and add
17-
.. % changes; it's therefore more important to add your changes to
18-
.. % Misc/NEWS than to this file.
19-
.. %
20-
.. % * This is not a complete list of every single change; completeness
21-
.. % is the purpose of Misc/NEWS. Some changes I consider too small
22-
.. % or esoteric to include. If such a change is added to the text,
23-
.. % I'll just remove it. (This is another reason you shouldn't spend
24-
.. % too much time on writing your addition.)
25-
.. %
26-
.. % * If you want to draw your new text to the attention of the
27-
.. % maintainer, add 'XXX' to the beginning of the paragraph or
28-
.. % section.
29-
.. %
30-
.. % * It's OK to just add a fragmentary note about a change. For
31-
.. % example: "XXX Describe the transmogrify() function added to the
32-
.. % socket module." The maintainer will research the change and
33-
.. % write the necessary text.
34-
.. %
35-
.. % * You can comment out your additions if you like, but it's not
36-
.. % necessary (especially when a final release is some months away).
37-
.. %
38-
.. % * Credit the author of a patch or bugfix. Just the name is
39-
.. % sufficient; the e-mail address isn't necessary.
40-
.. %
41-
.. % * It's helpful to add the bug/patch number as a comment:
42-
.. %
43-
.. % % Patch 12345
44-
.. % XXX Describe the transmogrify() function added to the socket
45-
.. % module.
46-
.. % (Contributed by P.Y. Developer.)
47-
.. %
48-
.. % This saves the maintainer the effort of going through the SVN log
49-
.. % when researching a change.
6+
:Release: 0.1
7+
8+
.. Rules for maintenance:
9+
10+
* Anyone can add text to this document. Do not spend very much time
11+
on the wording of your changes, because your text will probably
12+
get rewritten to some degree.
13+
14+
* The maintainer will go through Misc/NEWS periodically and add
15+
changes; it's therefore more important to add your changes to
16+
Misc/NEWS than to this file.
17+
18+
* This is not a complete list of every single change; completeness
19+
is the purpose of Misc/NEWS. Some changes I consider too small
20+
or esoteric to include. If such a change is added to the text,
21+
I'll just remove it. (This is another reason you shouldn't spend
22+
too much time on writing your addition.)
23+
24+
* If you want to draw your new text to the attention of the
25+
maintainer, add 'XXX' to the beginning of the paragraph or
26+
section.
27+
28+
* It's OK to just add a fragmentary note about a change. For
29+
example: "XXX Describe the transmogrify() function added to the
30+
socket module." The maintainer will research the change and
31+
write the necessary text.
32+
33+
* You can comment out your additions if you like, but it's not
34+
necessary (especially when a final release is some months away).
35+
36+
* Credit the author of a patch or bugfix. Just the name is
37+
sufficient; the e-mail address isn't necessary.
38+
39+
* It's helpful to add the bug/patch number as a comment:
40+
41+
% Patch 12345
42+
XXX Describe the transmogrify() function added to the socket
43+
module.
44+
(Contributed by P.Y. Developer.)
45+
46+
This saves the maintainer the effort of going through the SVN log
47+
when researching a change.
5048
5149
This article explains the new features in Python 3.0, comparing to 2.6
5250
(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
5957
you want to understand the complete implementation and design
6058
rationale, refer to the PEP for a particular new feature.
6159

62-
.. % Compare with previous release in 2 - 3 sentences here.
63-
.. % add hyperlink when the documentation becomes available online.
60+
.. Compare with previous release in 2 - 3 sentences here.
61+
.. add hyperlink when the documentation becomes available online.
6462
65-
.. % ======================================================================
66-
.. % Large, PEP-level features and changes should be described here.
67-
.. % Should there be a new section here for 3k migration?
68-
.. % Or perhaps a more general section describing module changes/deprecation?
69-
.. % sets module deprecated
70-
.. % ======================================================================
63+
.. ======================================================================
64+
.. Large, PEP-level features and changes should be described here.
65+
.. Should there be a new section here for 3k migration?
66+
.. Or perhaps a more general section describing module changes/deprecation?
67+
.. sets module deprecated
68+
.. ======================================================================
7169
7270
7371
Common Stumbling Blocks
@@ -128,7 +126,7 @@ changes to rarely used features.)
128126
Strings and Bytes
129127
=================
130128

131-
* There is only on string type; its name is ``str`` but its behavior
129+
* There is only one string type; its name is ``str`` but its behavior
132130
and implementation are more like ``unicode`` in 2.x.
133131

134132
* PEP 358: There is a new type, ``bytes``, to represent binary data
@@ -177,12 +175,12 @@ Exception Stuff
177175
===============
178176

179177
* PEP 352: Exceptions must derive from BaseException. This is the
180-
root of the exception hierarchy; only Exception,
178+
root of the exception hierarchy.
181179

182180
* StandardException was removed (already in 2.6).
183181

184-
* Dropping sequence behavior and ``.message`` attribute of exception
185-
instances.
182+
* Dropping sequence behavior (slicing!) and ``.message`` attribute of
183+
exception instances.
186184

187185
* PEP 3109: Raising exceptions. You must now use ``raise
188186
Exception(args)`` instead of ``raise Exception, args``.
@@ -232,13 +230,13 @@ language and built-in functions.
232230

233231
* ``__getslice__()`` and friends killed. The syntax ``a[i:j]`` now
234232
translates to ``a.__getitem__(slice(i, j))`` (or ``__setitem__``
235-
or ``__delitem``, depending on context).
233+
or ``__delitem__``, depending on context).
236234

237235
* PEP 3102: Keyword-only arguments. Named parameters occurring after
238236
``*args`` in the parameter list *must* be specified using keyword
239-
syntax in the call. You can also use ``*`` in the parameter list to
240-
indicate that you don't accept a variable-length argument list, but
241-
you do have keyword-only arguments.
237+
syntax in the call. You can also use a bare ``*`` in the parameter
238+
list to indicate that you don't accept a variable-length argument
239+
list, but you do have keyword-only arguments.
242240

243241
* PEP 3104: ``nonlocal`` statement. Using ``nonlocal x`` you can now
244242
assign directly to a variable in an outer (but non-global) scope.
@@ -259,16 +257,17 @@ language and built-in functions.
259257
``def foo(a, (b, c)): ...``. Use ``def foo(a, b_c): b, c = b_c``
260258
instead.
261259

262-
* PEP 3114: ``.next()`` renamed to ``.__next__()``.
260+
* PEP 3114: ``.next()`` renamed to ``.__next__()``, new builtin
261+
``next()`` to call the ``__next__()`` method on an object.
263262

264263
* PEP 3127: New octal literals; binary literals and ``bin()``.
265264
Instead of ``0666``, you write ``0o666``. The oct() function is
266265
modified accordingly. Also, ``0b1010`` equals 10, and ``bin(10)``
267-
returns ``"0b1010"``.
266+
returns ``"0b1010"``. ``0666`` is now a ``SyntaxError``.
268267

269268
* PEP 3132: Extended Iterable Unpacking. You can now write things
270269
like ``a, b, *rest = some_sequence``. And even ``*rest, a =
271-
stuff``. The ``rest`` variable is always a list; the right-hand
270+
stuff``. The ``rest`` object is always a list; the right-hand
272271
side may be any iterable.
273272

274273
* PEP 3135: New ``super()``. You can now invoke ``super()`` without
@@ -281,15 +280,15 @@ language and built-in functions.
281280
``.uppercase``) are gone. Use ``string.ascii_letters``
282281
etc. instead.
283282

284-
* Removed: apply(), callable(), coerce(), execfile(), file(),
285-
reduce(), reload().
283+
* Removed: ``apply()``, ``callable()``, ``coerce()``, ``execfile()``,
284+
``file()``, ``reduce()``, ``reload()``.
286285

287286
* Removed: ``dict.has_key()``.
288287

289288
* ``exec`` is now a function.
290289

291290

292-
.. % ======================================================================
291+
.. ======================================================================
293292
294293
295294
Optimizations
@@ -301,7 +300,7 @@ The net result of the 3.0 generalizations is that Python 3.0 runs the
301300
pystone benchmark around 25% slower than Python 2.5. There's room for
302301
improvement!
303302

304-
.. % ======================================================================
303+
.. ======================================================================
305304
306305
307306
New, Improved, and Deprecated Modules
@@ -316,10 +315,10 @@ through the CVS logs for all the details.
316315
* The ``cPickle`` module is gone. Use ``pickle`` instead. Eventually
317316
we'll have a transparent accelerator module.
318317

319-
.. % ======================================================================
320-
.. % whole new modules get described in \subsections here
318+
.. ======================================================================
319+
.. whole new modules get described in subsections here
321320
322-
.. % ======================================================================
321+
.. ======================================================================
323322
324323
325324
Build and C API Changes
@@ -331,17 +330,17 @@ Changes to Python's build process and to the C API include:
331330

332331
* PEP 3121: Extension Module Initialization & Finalization.
333332

334-
* PEP 3123: Making PyObject_HEAD conform to standard C.
333+
* PEP 3123: Making ``PyObject_HEAD`` conform to standard C.
335334

336-
.. % ======================================================================
335+
.. ======================================================================
337336
338337
339338
Port-Specific Changes
340339
---------------------
341340

342341
Platform-specific changes go here.
343342

344-
.. % ======================================================================
343+
.. ======================================================================
345344
346345
347346
.. _section-other:
@@ -358,7 +357,7 @@ Some of the more notable changes are:
358357

359358
* Details go here.
360359

361-
.. % ======================================================================
360+
.. ======================================================================
362361
363362
364363
Porting to Python 3.0
@@ -369,7 +368,7 @@ changes to your code:
369368

370369
* Everything is all in the details!
371370

372-
.. % ======================================================================
371+
.. ======================================================================
373372
374373
375374
.. _acks:
@@ -379,5 +378,5 @@ Acknowledgements
379378

380379
The author would like to thank the following people for offering
381380
suggestions, corrections and assistance with various drafts of this
382-
article: .
381+
article: Georg Brandl.
383382

0 commit comments

Comments
 (0)