diff options
Diffstat (limited to 'Doc/whatsnew/3.0.rst')
| -rw-r--r-- | Doc/whatsnew/3.0.rst | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/Doc/whatsnew/3.0.rst b/Doc/whatsnew/3.0.rst index 678ad80..fcdca04 100644 --- a/Doc/whatsnew/3.0.rst +++ b/Doc/whatsnew/3.0.rst @@ -1,5 +1,5 @@ **************************** - What's New In Python 3.0 + What's New In Python 3.0 **************************** .. XXX Add trademark info for Apple, Microsoft. @@ -10,45 +10,45 @@ .. $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 to some degree. - + * 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. (Note: I didn't get to this for 3.0. GvR.) - + * 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. (Due to time constraints I haven't managed to do this for 3.0. GvR.) - + * It's helpful to add the bug/patch number as a comment: - + % Patch 12345 XXX Describe the transmogrify() function added to the socket module. (Contributed by P.Y. Developer.) - + This saves the maintainer the effort of going through the SVN log when researching a change. (Again, I didn't get to this for 3.0. GvR.) @@ -819,7 +819,7 @@ Builtins need it; however, 99 percent of the time an explicit :keyword:`for` loop is more readable. -* Removed :func:`reload`. Use :func:`imp.reload`. +* Removed :func:`reload`. Use :func:`imp.reload`. * Removed. :meth:`dict.has_key` -- use the :keyword:`in` operator instead. |