Какие версии питона поддерживают windows 7

Ограничения есть только для виндовс хр, там максим можно поставить python3.4

А так лучше ставь не последнюю версию — python 3.9,
А поставь python 3.8.3 — там багов меньше, по крайней мере полгода я ей пользуюся

What is the last version which is available for Windows 7 (64bit) ?

3.1.1. Supported Versions¶

As specified in PEP 11, a Python release only supports a Windows platform
while Microsoft considers the platform under extended support. This means that
Python 3.7 supports Windows Vista and newer. If you require Windows XP
support then please install Python 3.4.

3.1.2. Installation Steps¶

Four Python 3.7 installers are available for download — two each for the
32-bit and 64-bit versions of the interpreter. The web installer is a small
initial download, and it will automatically download the required components as
necessary. The offline installer includes the components necessary for a
default installation and only requires an internet connection for optional
features. See Installing Without Downloading for other ways to avoid downloading
during installation.

After starting the installer, one of two options may be selected:

If you select “Install Now”:

• You will not need to be an administrator (unless a system update for the
  C Runtime Library is required or you install the Python Launcher for Windows for all
  users)
• Python will be installed into your user directory
• The Python Launcher for Windows will be installed according to the option at the bottom
  of the first page
• The standard library, test suite, launcher and pip will be installed
• If selected, the install directory will be added to your PATH
• Shortcuts will only be visible for the current user

Selecting “Customize installation” will allow you to select the features to
install, the installation location and other options or post-install actions.
To install debugging symbols or binaries, you will need to use this option.

To perform an all-users installation, you should select “Customize
installation”. In this case:

• You may be required to provide administrative credentials or approval
• Python will be installed into the Program Files directory
• The Python Launcher for Windows will be installed into the Windows directory
• Optional features may be selected during installation
• The standard library can be pre-compiled to bytecode
• If selected, the install directory will be added to the system PATH
• Shortcuts are available for all users

3.1.3. Removing the MAX_PATH Limitation¶

Windows historically has limited path lengths to 260 characters. This meant that
paths longer than this would not resolve and errors would result.

In the latest versions of Windows, this limitation can be expanded to
approximately 32,000 characters. Your administrator will need to activate the
“Enable Win32 long paths” group policy, or set the registry value
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem@LongPathsEnabled
to 1.

This allows the open() function, the os module and most other
path functionality to accept and return paths longer than 260 characters when
using strings. (Use of bytes as paths is deprecated on Windows, and this feature
is not available when using bytes.)

After changing the above option, no further configuration is required.

Changed in version 3.6: Support for long paths was enabled in Python.

3.1.4. Installing Without UI¶

All of the options available in the installer UI can also be specified from the
command line, allowing scripted installers to replicate an installation on many
machines without user interaction. These options may also be set without
suppressing the UI in order to change some of the defaults.

To completely hide the installer UI and install Python silently, pass the
/quiet option. To skip past the user interaction but still display
progress and errors, pass the /passive option. The /uninstall
option may be passed to immediately begin removing Python — no prompt will be
displayed.

All other options are passed as name=value, where the value is usually
0 to disable a feature, 1 to enable a feature, or a path. The full list
of available options is shown below.

For example, to silently install a default, system-wide Python installation,
you could use the following command (from an elevated command prompt):

python-3.6.0.exe /quiet InstallAllUsers=1 PrependPath=1 Include_test=0

To allow users to easily install a personal copy of Python without the test
suite, you could provide a shortcut with the following command. This will
display a simplified initial page and disallow customization:

python-3.6.0.exe InstallAllUsers=0 Include_launcher=0 Include_test=0
    SimpleInstall=1 SimpleInstallDescription="Just for me, no test suite."

(Note that omitting the launcher also omits file associations, and is only
recommended for per-user installs when there is also a system-wide installation
that included the launcher.)

The options listed above can also be provided in a file named unattend.xml
alongside the executable. This file specifies a list of options and values.
When a value is provided as an attribute, it will be converted to a number if
possible. Values provided as element text are always left as strings. This
example file sets the same options and the previous example:

<Options>
    <Option Name="InstallAllUsers" Value="no" />
    <Option Name="Include_launcher" Value="0" />
    <Option Name="Include_test" Value="no" />
    <Option Name="SimpleInstall" Value="yes" />
    <Option Name="SimpleInstallDescription">Just for me, no test suite</Option>
</Options>

3.1.5. Installing Without Downloading¶

As some features of Python are not included in the initial installer download,
selecting those features may require an internet connection. To avoid this
need, all possible components may be downloaded on-demand to create a complete
layout that will no longer require an internet connection regardless of the
selected features. Note that this download may be bigger than required, but
where a large number of installations are going to be performed it is very
useful to have a locally cached copy.

Execute the following command from Command Prompt to download all possible
required files. Remember to substitute python-3.6.0.exe for the actual
name of your installer, and to create layouts in their own directories to
avoid collisions between files with the same name.

python-3.6.0.exe /layout [optional target directory]

You may also specify the /quiet option to hide the progress display.

3.1.6. Modifying an install¶

Once Python has been installed, you can add or remove features through the
Programs and Features tool that is part of Windows. Select the Python entry and
choose “Uninstall/Change” to open the installer in maintenance mode.

“Modify” allows you to add or remove features by modifying the checkboxes —
unchanged checkboxes will not install or remove anything. Some options cannot be
changed in this mode, such as the install directory; to modify these, you will
need to remove and then reinstall Python completely.

“Repair” will verify all the files that should be installed using the current
settings and replace any that have been removed or modified.

“Uninstall” will remove Python entirely, with the exception of the
Python Launcher for Windows, which has its own entry in Programs and Features.

3.1.7. Other Platforms¶

With ongoing development of Python, some platforms that used to be supported
earlier are no longer supported (due to the lack of users or developers).
Check PEP 11 for details on all unsupported platforms.

• Windows CE is still supported.
• The Cygwin installer offers to install the Python
  interpreter as well (cf. Cygwin package source, Maintainer releases)

See Python for Windows
for detailed information about platforms with pre-compiled installers.

3.3.1. Excursus: Setting environment variables¶

Windows allows environment variables to be configured permanently at both the
User level and the System level, or temporarily in a command prompt.

To temporarily set environment variables, open Command Prompt and use the
set command:

C:\>set PATH=C:\Program Files\Python 3.6;%PATH%
C:\>set PYTHONPATH=%PYTHONPATH%;C:\My_python_lib
C:\>python

These changes will apply to any further commands executed in that console, and
will be inherited by any applications started from the console.

Including the variable name within percent signs will expand to the existing
value, allowing you to add your new value at either the start or the end.
Modifying PATH by adding the directory containing
python.exe to the start is a common way to ensure the correct version
of Python is launched.

To permanently modify the default environment variables, click Start and search
for ‘edit environment variables’, or open System properties, Advanced
system settings and click the Environment Variables button.
In this dialog, you can add or modify User and System variables. To change
System variables, you need non-restricted access to your machine
(i.e. Administrator rights).

3.3.2. Finding the Python executable¶

Changed in version 3.5.

Besides using the automatically created start menu entry for the Python
interpreter, you might want to start Python in the command prompt. The
installer has an option to set that up for you.

On the first page of the installer, an option labelled “Add Python to PATH”
may be selected to have the installer add the install location into the
PATH. The location of the Scripts\ folder is also added.
This allows you to type python to run the interpreter, and
pip for the package installer. Thus, you can also execute your
scripts with command line options, see Command line documentation.

If you don’t enable this option at install time, you can always re-run the
installer, select Modify, and enable it. Alternatively, you can manually
modify the PATH using the directions in Excursus: Setting environment variables. You
need to set your PATH environment variable to include the directory
of your Python installation, delimited by a semicolon from other entries. An
example variable could look like this (assuming the first two entries already
existed):

C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files\Python 3.6

3.4.1. Getting started¶

'py' is not recognized as an internal or external command,
operable program or batch file.

#! python
import sys
sys.stdout.write("hello from Python %s\n" % (sys.version,))

3.4.2. Shebang Lines¶

If the first line of a script file starts with #!, it is known as a
“shebang” line. Linux and other Unix like operating systems have native
support for such lines and they are commonly used on such systems to indicate
how a script should be executed. This launcher allows the same facilities to
be used with Python scripts on Windows and the examples above demonstrate their
use.

To allow shebang lines in Python scripts to be portable between Unix and
Windows, this launcher supports a number of ‘virtual’ commands to specify
which interpreter to use. The supported virtual commands are:

• /usr/bin/env python
• /usr/bin/python
• /usr/local/bin/python
• python

For example, if the first line of your script starts with

The default Python will be located and used. As many Python scripts written
to work on Unix will already have this line, you should find these scripts can
be used by the launcher without modification. If you are writing a new script
on Windows which you hope will be useful on Unix, you should use one of the
shebang lines starting with /usr.

Any of the above virtual commands can be suffixed with an explicit version
(either just the major version, or the major and minor version) — for example
/usr/bin/python2.7 — which will cause that specific version to be located
and used.

The /usr/bin/env form of shebang line has one further special property.
Before looking for installed Python interpreters, this form will search the
executable PATH for a Python executable. This corresponds to the
behaviour of the Unix env program, which performs a PATH search.

3.4.3. Arguments in shebang lines¶

The shebang lines can also specify additional options to be passed to the
Python interpreter. For example, if you have a shebang line:

Then Python will be started with the -v option

3.4.4. Customization¶

[defaults]
python=3
python3=3.1

3.4.5. Diagnostics¶

If an environment variable PYLAUNCH_DEBUG is set (to any value), the
launcher will print diagnostic information to stderr (i.e. to the console).
While this information manages to be simultaneously verbose and terse, it
should allow you to see what versions of Python were located, why a
particular version was chosen and the exact command-line used to execute the
target Python.

Changed in version 3.6:

• Adds ._pth file support and removes applocal option from
  pyvenv.cfg.
• Adds pythonXX.zip as a potential landmark when directly adjacent
  to the executable.

Deprecated since version 3.6:

Modules specified in the registry under Modules (not PythonPath)
may be imported by importlib.machinery.WindowsRegistryFinder.
This finder is enabled on Windows in 3.6.0 and earlier, but may need to
be explicitly added to sys.meta_path in the future.

3.6.1. PyWin32¶

The PyWin32 module by Mark Hammond
is a collection of modules for advanced Windows-specific support. This includes
utilities for:

• Component Object Model (COM)
• Win32 API calls
• Registry
• Event log
• Microsoft Foundation Classes (MFC)
  user interfaces

PythonWin is a sample MFC application
shipped with PyWin32. It is an embeddable IDE with a built-in debugger.

3.6.2. cx_Freeze¶

cx_Freeze is a distutils
extension (see Extending Distutils) which wraps Python scripts into
executable Windows programs (*.exe files). When you have done this,
you can distribute your application without requiring your users to install
Python.

3.6.3. WConio¶

Since Python’s advanced terminal handling layer, curses, is restricted to
Unix-like systems, there is a library exclusive to Windows as well: Windows
Console I/O for Python.

WConio is a wrapper for
Turbo-C’s CONIO.H, used to create text user interfaces.

Note

The embedded distribution does not include the Microsoft C Runtime and it is
the responsibility of the application installer to provide this. The
runtime may have already been installed on a user’s system previously or
automatically via Windows Update, and can be detected by finding
ucrtbase.dll in the system directory.

3.8.1. Python Application¶

An application written in Python does not necessarily require users to be aware
of that fact. The embedded distribution may be used in this case to include a
private version of Python in an install package. Depending on how transparent it
should be (or conversely, how professional it should appear), there are two
options.

Using a specialized executable as a launcher requires some coding, but provides
the most transparent experience for users. With a customized launcher, there are
no obvious indications that the program is running on Python: icons can be
customized, company and version information can be specified, and file
associations behave properly. In most cases, a custom launcher should simply be
able to call Py_Main with a hard-coded command line.

The simpler approach is to provide a batch file or generated shortcut that
directly calls the python.exe or pythonw.exe with the required
command-line arguments. In this case, the application will appear to be Python
and not its actual name, and users may have trouble distinguishing it from other
running Python processes or file associations.

With the latter approach, packages should be installed as directories alongside
the Python executable to ensure they are available on the path. With the
specialized launcher, packages can be located in other locations as there is an
opportunity to specify the search path before launching the application.

3.8.2. Embedding Python¶

Applications written in native code often require some form of scripting
language, and the embedded Python distribution can be used for this purpose. In
general, the majority of the application is in native code, and some part will
either invoke python.exe or directly use python3.dll. For either case,
extracting the embedded distribution to a subdirectory of the application
installation is sufficient to provide a loadable Python interpreter.

As with the application use, packages can be installed to any location as there
is an opportunity to specify search paths before initializing the interpreter.
Otherwise, there is no fundamental differences between using the embedded
distribution and a regular installation.