/proc/self/root/proc/thread-self/root/proc/1/task/1/root/usr/share/doc/python3-libs
This explorer reads the filesystem of the server it runs on, so /workspace/user isn't present here. Browsing and the terminal still work against this server's own disk from /.
This is Python version 3.9.25============================= .. image:: https://travis-ci.org/python/cpython.svg?branch=3.9 :alt: CPython build status on Travis CI :target: https://travis-ci.org/python/cpython .. image:: https://github.com/python/cpython/workflows/Tests/badge.svg :alt: CPython build status on GitHub Actions :target: https://github.com/python/cpython/actions .. image:: https://dev.azure.com/python/cpython/_apis/build/status/Azure%20Pipelines%20CI?branchName=3.9 :alt: CPython build status on Azure DevOps :target: https://dev.azure.com/python/cpython/_build/latest?definitionId=4&branchName=3.9 .. image:: https://codecov.io/gh/python/cpython/branch/3.9/graph/badge.svg :alt: CPython code coverage on Codecov :target: https://codecov.io/gh/python/cpython .. image:: https://img.shields.io/badge/discourse-join_chat-brightgreen.svg :alt: Python Discourse chat :target: https://discuss.python.org/ Copyright © 2001-2023 Python Software Foundation. All rights reserved. See the end of this file for further copyright and license information. .. contents:: General Information------------------- - Website: https://www.python.org- Source code: https://github.com/python/cpython- Issue tracker: https://bugs.python.org- Documentation: https://docs.python.org- Developer's Guide: https://devguide.python.org/ Contributing to CPython----------------------- For more complete instructions on contributing to CPython development,see the `Developer Guide`_. .. _Developer Guide: https://devguide.python.org/ Using Python------------ Installable Python kits, and information about using Python, are available at`python.org`_. .. _python.org: https://www.python.org/ Build Instructions------------------ On Unix, Linux, BSD, macOS, and Cygwin:: ./configure make make test sudo make install This will install Python as ``python3``. You can pass many options to the configure script; run ``./configure --help``to find out more. On macOS case-insensitive file systems and on Cygwin,the executable is called ``python.exe``; elsewhere it's just ``python``. Building a complete Python installation requires the use of variousadditional third-party libraries, depending on your build platform andconfigure options. Not all standard library modules are buildable oruseable on all platforms. Refer to the`Install dependencies <https://devguide.python.org/setup/#install-dependencies>`_section of the `Developer Guide`_ for current detailed information ondependencies for various Linux distributions and macOS. On macOS, there are additional configure and build options relatedto macOS framework and universal builds. Refer to `Mac/README.rst<https://github.com/python/cpython/blob/3.9/Mac/README.rst>`_. On Windows, see `PCbuild/readme.txt<https://github.com/python/cpython/blob/3.9/PCbuild/readme.txt>`_. If you wish, you can create a subdirectory and invoke configure from there.For example:: mkdir debug cd debug ../configure --with-pydebug make make test (This will fail if you *also* built at the top-level directory. You should doa ``make clean`` at the top-level first.) To get an optimized build of Python, ``configure --enable-optimizations``before you run ``make``. This sets the default make targets up to enableProfile Guided Optimization (PGO) and may be used to auto-enable Link TimeOptimization (LTO) on some platforms. For more details, see the sectionsbelow. Profile Guided Optimization^^^^^^^^^^^^^^^^^^^^^^^^^^^ PGO takes advantage of recent versions of the GCC or Clang compilers. If used,either via ``configure --enable-optimizations`` or by manually running``make profile-opt`` regardless of configure flags, the optimized buildprocess will perform the following steps: The entire Python directory is cleaned of temporary files that may haveresulted from a previous compilation. An instrumented version of the interpreter is built, using suitable compilerflags for each flavor. Note that this is just an intermediary step. Thebinary resulting from this step is not good for real-life workloads as it hasprofiling instructions embedded inside. After the instrumented interpreter is built, the Makefile will run a trainingworkload. This is necessary in order to profile the interpreter's execution.Note also that any output, both stdout and stderr, that may appear at this stepis suppressed. The final step is to build the actual interpreter, using the informationcollected from the instrumented one. The end result will be a Python binarythat is optimized; suitable for distribution or production installation. Link Time Optimization^^^^^^^^^^^^^^^^^^^^^^ Enabled via configure's ``--with-lto`` flag. LTO takes advantage of theability of recent compiler toolchains to optimize across the otherwisearbitrary ``.o`` file boundary when building final executables or sharedlibraries for additional performance gains. What's New---------- We have a comprehensive overview of the changes in the `What's New in Python3.9 <https://docs.python.org/3.9/whatsnew/3.9.html>`_ document. For a moredetailed change log, read `Misc/NEWS<https://github.com/python/cpython/blob/3.9/Misc/NEWS.d>`_, but a fullaccounting of changes can only be gleaned from the `commit history<https://github.com/python/cpython/commits/3.9>`_. If you want to install multiple versions of Python, see the section belowentitled "Installing multiple versions". Documentation------------- `Documentation for Python 3.9 <https://docs.python.org/3.9/>`_ is online,updated daily. It can also be downloaded in many formats for faster access. The documentationis downloadable in HTML, PDF, and reStructuredText formats; the latter versionis primarily for documentation authors, translators, and people with specialformatting requirements. For information about building Python's documentation, refer to `Doc/README.rst<https://github.com/python/cpython/blob/3.9/Doc/README.rst>`_. Converting From Python 2.x to 3.x--------------------------------- Significant backward incompatible changes were made for the release of Python3.0, which may cause programs written for Python 2 to fail when run with Python3. For more information about porting your code from Python 2 to Python 3, seethe `Porting HOWTO <https://docs.python.org/3/howto/pyporting.html>`_. Testing------- To test the interpreter, type ``make test`` in the top-level directory. Thetest set produces some output. You can generally ignore the messages aboutskipped tests due to optional features which can't be imported. If a messageis printed about a failed test or a traceback or core dump is produced,something is wrong. By default, tests are prevented from overusing resources like disk space andmemory. To enable these tests, run ``make testall``. If any tests fail, you can re-run the failing test(s) in verbose mode. Forexample, if ``test_os`` and ``test_gdb`` failed, you can run:: make test TESTOPTS="-v test_os test_gdb" If the failure persists and appears to be a problem with Python rather thanyour environment, you can `file a bug report <https://bugs.python.org>`_ andinclude relevant output from that command to show the issue. See `Running & Writing Tests <https://devguide.python.org/runtests/>`_for more on running tests. Installing multiple versions---------------------------- On Unix and Mac systems if you intend to install multiple versions of Pythonusing the same installation prefix (``--prefix`` argument to the configurescript) you must take care that your primary python executable is notoverwritten by the installation of a different version. All files anddirectories installed using ``make altinstall`` contain the major and minorversion and can thus live side-by-side. ``make install`` also creates``${prefix}/bin/python3`` which refers to ``${prefix}/bin/pythonX.Y``. If youintend to install multiple versions using the same prefix you must decide whichversion (if any) is your "primary" version. Install that version using ``makeinstall``. 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 theprimary version, you would execute ``make install`` in your 3.9 build directoryand ``make altinstall`` in the others. Issue Tracker and Mailing List------------------------------ Bug reports are welcome! You can use the `issue tracker<https://bugs.python.org>`_ to report bugs, and/or submit pull requests `onGitHub <https://github.com/python/cpython>`_. You can also follow development discussion on the `python-dev mailing list<https://mail.python.org/mailman/listinfo/python-dev/>`_. Proposals for enhancement------------------------- If you have a proposal to change Python, you may want to send an email to the`comp.lang.python`_ or `python-ideas`_ mailing lists for initial feedback. APython Enhancement Proposal (PEP) may be submitted if your idea gains ground.All current PEPs, as well as guidelines for submitting a new PEP, are listed at`python.org/dev/peps/ <https://www.python.org/dev/peps/>`_. .. _python-ideas: https://mail.python.org/mailman/listinfo/python-ideas/.. _comp.lang.python: https://mail.python.org/mailman/listinfo/python-list Release Schedule---------------- See :pep:`596` for Python 3.9 release details. Copyright and License Information--------------------------------- Copyright © 2001-2023 Python Software Foundation. All rights reserved. Copyright © 2000 BeOpen.com. All rights reserved. Copyright © 1995-2001 Corporation for National Research Initiatives. Allrights reserved. Copyright © 1991-1995 Stichting Mathematisch Centrum. All rights reserved. See the file "LICENSE" for information on the history of this software, terms &conditions for usage, and a DISCLAIMER OF ALL WARRANTIES. This Python distribution contains *no* GNU General Public License (GPL) code,so it may be used in proprietary projects. There are interfaces to some GNUcode but these are entirely optional. All trademarks referenced herein are property of their respective holders.