Python 3.10.0a0

Doc/tutorial/interpreter.rst

@@ -10,21 +10,21 @@ Using the Python Interpreter
 Invoking the Interpreter
 ========================
 
-The Python interpreter is usually installed as :file:`/usr/local/bin/python3.9`
+The Python interpreter is usually installed as :file:`/usr/local/bin/python3.10`
 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.9
+ python3.10
 
 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
 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.9` command will be available. If you have
+<windows-store>`, the :file:`python3.10` 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.9
- Python 3.9 (default, June 4 2019, 09:25:04)
+ $ python3.10
+ Python 3.10 (default, June 4 2019, 09:25:04)
  [GCC 4.8.2] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>>

Doc/tutorial/stdlib.rst

@@ -15,7 +15,7 @@ operating system::
 
  >>> import os
  >>> os.getcwd() # Return the current working directory
- 'C:\\Python39'
+ 'C:\\Python310'
  >>> os.chdir('/server/accesslogs') # Change current working directory
  >>> os.system('mkdir today') # Run the command mkdir in the system shell
  0

Doc/tutorial/stdlib2.rst

@@ -278,7 +278,7 @@ applications include caching objects that are expensive to create::
  Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  d['primary'] # entry was automatically removed
- File "C:/python39/lib/weakref.py", line 46, in __getitem__
+ File "C:/python310/lib/weakref.py", line 46, in __getitem__
  o = self.data[key]()
  KeyError: 'primary'
 

Include/patchlevel.h

@@ -17,13 +17,13 @@
 /* Version parsed out into numeric values */
 /*--start constants--*/
 #define PY_MAJOR_VERSION 3
-#define PY_MINOR_VERSION 9
+#define PY_MINOR_VERSION 10
 #define PY_MICRO_VERSION 0
 #define PY_RELEASE_LEVEL PY_RELEASE_LEVEL_ALPHA
-#define PY_RELEASE_SERIAL 6
+#define PY_RELEASE_SERIAL 0
 
 /* Version as a string */
-#define PY_VERSION "3.9.0a6+"
+#define PY_VERSION "3.10.0a0"
 /*--end constants--*/
 
 /* Version as a single 4-byte hex number, e.g. 0x010502B2 == 1.5.2b2.

README.rst

@@ -1,5 +1,5 @@
-This is Python version 3.9.0 alpha 6
-====================================
+This is Python version 3.10.0 alpha 0
+=====================================
 
 .. image:: https://travis-ci.org/python/cpython.svg?branch=master
  :alt: CPython build status on Travis CI
@@ -141,7 +141,7 @@ What's New
 ----------
 
 We have a comprehensive overview of the changes in the `What's New in Python
-3.9 <https://docs.python.org/3.9/whatsnew/3.9.html>`_ document. For a more
+3.10 <https://docs.python.org/3.10/whatsnew/3.10.html>`_ document. For a more
 detailed change log, read `Misc/NEWS
 <https://github.com/python/cpython/blob/master/Misc/NEWS.d>`_, but a full
 accounting of changes can only be gleaned from the `commit history
@@ -154,7 +154,7 @@ entitled "Installing multiple versions".
 Documentation
 -------------
 
-`Documentation for Python 3.9 <https://docs.python.org/3.9/>`_ is online,
+`Documentation for Python 3.10 <https://docs.python.org/3.10/>`_ is online,
 updated daily.
 
 It can also be downloaded in many formats for faster access. The documentation
@@ -213,8 +213,8 @@ intend to install multiple versions using the same prefix you must decide which
 version (if any) is your "primary" version. Install that version using ``make
 install``. Install all other versions using ``make altinstall``.
 
-For example, if you want to install Python 2.7, 3.6, and 3.9 with 3.9 being the
-primary version, you would execute ``make install`` in your 3.9 build directory
+For example, if you want to install Python 2.7, 3.6, and 3.10 with 3.10 being the
+primary version, you would execute ``make install`` in your 3.10 build directory
 and ``make altinstall`` in the others.
 
 

configure.ac

@@ -3,7 +3,7 @@ dnl * Please run autoreconf to test your changes! *
 dnl ***********************************************
 
 # Set VERSION so we only need to edit in one place (i.e., here)
-m4_define(PYTHON_VERSION, 3.9)
+m4_define(PYTHON_VERSION, 3.10)
 
 AC_PREREQ([2.69])