# Python 3 in SUSE

## Subpackages

Python 3 is split into several subpackages, based on external
dependencies. The main package `python3` has soft dependencies on all
subpackages needed to assemble the standard library; however, these
might not all be installed by default.

If you attempt to import a module that is currently not installed, an
ImportError is thrown, with instructions to install the missing
subpackage. Installing the subpackage might result in installing
libraries that the subpackage requires to function.


## ensurepip

The `ensurepip` module from Python 3 standard library (PEP 453) is
supposed to deploy a bundled copy of the pip installer. This makes no
sense in a managed distribution like SUSE. Instead, you need to install
package `python3-pip`. Usually this will be installed automatically with
`python3`.

Using `ensurepip` when pip is not installed will result in an
ImportError with instructions to install `python3-pip`.


## Documentation

You can find documentation in seprarate packages: python3-doc and
python3-doc-pdf. These contan following documents:

> Tutorial, What's New in Python, Global Module Index, Library Reference,
> Macintosh Module Reference, Installing Python Modules, Distributing Python
> Modules, Language Reference, Extending and Embedding, Python/C API,
> Documenting Python 

The python3-doc package constains many text files from source tarball.


## Interactive mode

Interactive mode is by default enhanced with of history and command completion.
If you don't like these features, you can unset the PYTHONSTARTUP variable
in your .profile or disable it system wide in /etc/profile.d/python.sh.


## Update process

- submit the python313 version update and the matching python3
  rebuild/update together.

- Before/when staging the upgrade:
  - Update python313 to the new upstream version.
  - Trigger a new python3 build after python313-base and python313-devel
    of that version are available.
  - Verify python3-base now requires the new exact base version:
      ```sh
      rpm -qp --requires python3-base-*.rpm | grep 'python313-base'
      ```
    - Avoid relying on an incremental rebuild of reverse dependencies; use
      a project/repository binary wipe when testing the coordinated
      update.
  - Watch python3 specifically before looking at downstream failures,
    since it supplies the generic compatibility namespace.
  - No spec change should be needed: the current BuildRequires split is
    designed to make the bootstrap ordering possible.
