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

Skip to content

Commit 6e6565b

Browse files
committed
Whatsnew begins afresh
1 parent 8dad7df commit 6e6565b

1 file changed

Lines changed: 99 additions & 0 deletions

File tree

Doc/whatsnew/3.2.rst

Lines changed: 99 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,99 @@
1+
****************************
2+
What's New In Python 3.1
3+
****************************
4+
5+
:Author: Raymond Hettinger
6+
:Release: |release|
7+
:Date: |today|
8+
9+
.. $Id$
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.
50+
51+
This article explains the new features in Python 3.2, compared to 3.1.
52+
53+
54+
PEP XXX: Stub
55+
=============
56+
57+
58+
Other Language Changes
59+
======================
60+
61+
Some smaller changes made to the core Python language are:
62+
63+
* Stub
64+
65+
66+
New, Improved, and Deprecated Modules
67+
=====================================
68+
69+
* Stub
70+
71+
72+
Optimizations
73+
=============
74+
75+
Major performance enhancements have been added:
76+
77+
* Stub
78+
79+
IDLE
80+
====
81+
82+
* Stub
83+
84+
85+
Build and C API Changes
86+
=======================
87+
88+
Changes to Python's build process and to the C API include:
89+
90+
* Stub
91+
92+
93+
Porting to Python 3.1
94+
=====================
95+
96+
This section lists previously described changes and other bugfixes
97+
that may require changes to your code:
98+
99+
* Stub

0 commit comments

Comments
 (0)