summaryrefslogtreecommitdiffstats
path: root/Doc
diff options
context:
space:
mode:
authorThomas Wouters <thomas@python.org>2023-05-22 19:15:32 (GMT)
committerThomas Wouters <thomas@python.org>2023-05-22 19:15:32 (GMT)
commit500b0f4814e05b918f485ceebf9c7be9a52ad469 (patch)
treed53bee1faf93aa13b96498682e7e278669d45413 /Doc
parent5612078f68e9688fbf3b1d8565abc79b77501000 (diff)
downloadcpython-500b0f4814e05b918f485ceebf9c7be9a52ad469.zip
cpython-500b0f4814e05b918f485ceebf9c7be9a52ad469.tar.gz
cpython-500b0f4814e05b918f485ceebf9c7be9a52ad469.tar.bz2
Python 3.13.0a0
Diffstat (limited to 'Doc')
-rw-r--r--Doc/tutorial/interpreter.rst10
-rw-r--r--Doc/whatsnew/3.13132
2 files changed, 137 insertions, 5 deletions
diff --git a/Doc/tutorial/interpreter.rst b/Doc/tutorial/interpreter.rst
index b71c610..42ebf2b 100644
--- a/Doc/tutorial/interpreter.rst
+++ b/Doc/tutorial/interpreter.rst
@@ -10,13 +10,13 @@ Using the Python Interpreter
Invoking the Interpreter
========================
-The Python interpreter is usually installed as :file:`/usr/local/bin/python3.12`
+The Python interpreter is usually installed as :file:`/usr/local/bin/python3.13`
on those machines where it is available; putting :file:`/usr/local/bin` in your
Unix shell's search path makes it possible to start it by typing the command:
.. code-block:: text
- python3.12
+ python3.13
to the shell. [#]_ Since the choice of the directory where the interpreter lives
is an installation option, other places are possible; check with your local
@@ -24,7 +24,7 @@ Python guru or system administrator. (E.g., :file:`/usr/local/python` is a
popular alternative location.)
On Windows machines where you have installed Python from the :ref:`Microsoft Store
-<windows-store>`, the :file:`python3.12` command will be available. If you have
+<windows-store>`, the :file:`python3.13` command will be available. If you have
the :ref:`py.exe launcher <launcher>` installed, you can use the :file:`py`
command. See :ref:`setting-envvars` for other ways to launch Python.
@@ -97,8 +97,8 @@ before printing the first prompt:
.. code-block:: shell-session
- $ python3.12
- Python 3.12 (default, April 4 2022, 09:25:04)
+ $ python3.13
+ Python 3.13 (default, April 4 2023, 09:25:04)
[GCC 10.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>>
diff --git a/Doc/whatsnew/3.13 b/Doc/whatsnew/3.13
new file mode 100644
index 0000000..af331c4
--- /dev/null
+++ b/Doc/whatsnew/3.13
@@ -0,0 +1,132 @@
+
+****************************
+ What's New In Python 3.13
+****************************
+
+: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 issue number as a comment:
+
+ XXX Describe the transmogrify() function added to the socket
+ module.
+ (Contributed by P.Y. Developer in :gh:`12345`.)
+
+ This saves the maintainer the effort of going through the VCS log
+ when researching a change.
+
+This article explains the new features in Python 3.13, compared to 3.12.
+
+For full details, see the :ref:`changelog <changelog>`.
+
+.. note::
+
+ Prerelease users should be aware that this document is currently in draft
+ form. It will be updated substantially as Python 3.13 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.13.
+ Brevity is key.
+
+
+.. PEP-sized items next.
+
+
+
+New Features
+============
+
+
+
+Other Language Changes
+======================
+
+
+
+New Modules
+===========
+
+* None yet.
+
+
+Improved Modules
+================
+
+
+Optimizations
+=============
+
+
+
+
+Deprecated
+==========
+
+
+
+Removed
+=======
+
+
+
+Porting to Python 3.13
+======================
+
+This section lists previously described changes and other bugfixes
+that may require changes to your code.
+
+
+Build Changes
+=============
+
+
+C API Changes
+=============
+
+New Features
+------------
+
+Porting to Python 3.13
+----------------------
+
+Deprecated
+----------
+
+Removed
+-------
+