Update Doc build to 3.8

This commit is contained in:
Ned Deily 2018-01-31 18:12:38 -05:00
parent 5489bdad51
commit 07a1892f82
4 changed files with 119 additions and 1 deletions

View File

@ -10,7 +10,8 @@
'(?:release/\\d.\\d[\\x\\d\\.]*)'];
var all_versions = {
'3.7': 'dev (3.7)',
'3.8': 'dev (3.8)',
'3.7': 'pre (3.7)',
'3.6': '3.6',
'3.5': '3.5',
'2.7': '2.7',

View File

@ -2,6 +2,7 @@
<p><a href="{{ pathto('download') }}">{% trans %}Download these documents{% endtrans %}</a></p>
<h3>{% trans %}Docs for other versions{% endtrans %}</h3>
<ul>
<li><a href="https://docs.python.org/3.7/">{% trans %}Python 3.7 (pre-release){% endtrans %}</a></li>
<li><a href="https://docs.python.org/3.6/">{% trans %}Python 3.6 (stable){% endtrans %}</a></li>
<li><a href="https://docs.python.org/3.5/">{% trans %}Python 3.5 (stable){% endtrans %}</a></li>
<li><a href="https://docs.python.org/2.7/">{% trans %}Python 2.7 (stable){% endtrans %}</a></li>

115
Doc/whatsnew/3.8.rst Normal file
View File

@ -0,0 +1,115 @@
****************************
What's New In Python 3.8
****************************
:Release: |release|
:Date: |today|
.. 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.
* 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 bug/patch number as a comment:
XXX Describe the transmogrify() function added to the socket
module.
(Contributed by P.Y. Developer in :issue:`12345`.)
This saves the maintainer the effort of going through the Mercurial log
when researching a change.
This article explains the new features in Python 3.8, compared to 3.7.
For full details, see the :source:`Misc/NEWS` file.
.. note::
Prerelease users should be aware that this document is currently in draft
form. It will be updated substantially as Python 3.8 moves towards release,
so it's worth checking back even after reading earlier versions.
Summary -- Release highlights
=============================
.. This section singles out the most important changes in Python 3.8.
Brevity is key.
.. PEP-sized items next.
New Features
============
Other Language Changes
======================
New Modules
===========
* None yet.
Improved Modules
================
Optimizations
=============
Build and C API Changes
=======================
Deprecated
==========
Removed
=======
Porting to Python 3.8
=====================
This section lists previously described changes and other bugfixes
that may require changes to your code.

View File

@ -11,6 +11,7 @@ anyone wishing to stay up-to-date after a new release.
.. toctree::
:maxdepth: 2
3.8.rst
3.7.rst
3.6.rst
3.5.rst