| Nov | DEC | Jan |
| 15 | ||
| 2018 | 2019 | 2020 |
COLLECTED BY
Collection: Live Web Proxy Crawls
| Type | Name | Latest commit message | Commit time |
|---|---|---|---|
| Failed to load latest commit information. | |||
|
.azure-pipelines |
|
|
|
|
.github |
|
|
|
|
Doc |
|
|
|
|
Grammar |
|
|
|
|
Include |
|
|
|
|
Lib |
|
|
|
|
Mac |
|
|
|
|
Misc |
|
|
|
|
Modules |
|
|
|
|
Objects |
|
|
|
|
PC |
|
|
|
|
PCbuild |
|
|
|
|
Parser |
|
|
|
|
Programs |
|
|
|
|
Python |
|
|
|
|
Tools |
|
|
|
|
m4 |
|
|
|
|
.gitattributes |
|
|
|
|
.gitignore |
|
|
|
|
.travis.yml |
|
|
|
|
CODE_OF_CONDUCT.md |
|
|
|
|
LICENSE |
|
|
|
|
Makefile.pre.in |
|
|
|
|
README.rst |
|
|
|
|
aclocal.m4 |
|
|
|
|
config.guess |
|
|
|
|
config.sub |
|
|
|
|
configure |
|
|
|
|
configure.ac |
|
|
|
|
install-sh |
|
|
|
|
netlify.toml |
|
|
|
|
pyconfig.h.in |
|
|
|
|
setup.py |
|
|
Copyright (c) 2001-2019 Python Software Foundation. All rights reserved.
See the end of this file for further copyright and license information.
Contents
●General Information
●Contributing to CPython
●Using Python
●Build Instructions
●Profile Guided Optimization
●Link Time Optimization
●What's New
●Documentation
●Converting From Python 2.x to 3.x
●Testing
●Installing multiple versions
●Issue Tracker and Mailing List
●Proposals for enhancement
●Release Schedule
●Copyright and License Information
./configure make make test sudo make installThis 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 various
additional third-party libraries, depending on your build platform and
configure options. Not all standard library modules are buildable or
useable on all platforms. Refer to the
Install dependencies
section of the Developer Guide for current detailed information on
dependencies for various Linux distributions and macOS.
On macOS, there are additional configure and build options related
to macOS framework and universal builds. Refer to Mac/README.rst.
On Windows, see 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 do a
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 enable
Profile Guided Optimization (PGO) and may be used to auto-enable Link Time
Optimization (LTO) on some platforms. For more details, see the sections
below.
configure --enable-optimizations or by manually running
make profile-opt regardless of configure flags, the optimized build
process will perform the following steps:
The entire Python directory is cleaned of temporary files that may have
resulted from a previous compilation.
An instrumented version of the interpreter is built, using suitable compiler
flags for each flavour. Note that this is just an intermediary step. The
binary resulting from this step is not good for real life workloads as it has
profiling instructions embedded inside.
After the instrumented interpreter is built, the Makefile will run a training
workload. This is necessary in order to profile the interpreter execution.
Note also that any output, both stdout and stderr, that may appear at this step
is suppressed.
The final step is to build the actual interpreter, using the information
collected from the instrumented one. The end result will be a Python binary
that is optimized; suitable for distribution or production installation.
--with-lto flag. LTO takes advantage of the
ability of recent compiler toolchains to optimize across the otherwise
arbitrary .o file boundary when building final executables or shared
libraries for additional performance gains.
make test in the top-level directory. The
test set produces some output. You can generally ignore the messages about
skipped tests due to optional features which can't be imported. If a message
is 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 and
memory. To enable these tests, run make testall.
If any tests fail, you can re-run the failing test(s) in verbose mode. For
example, 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 than your environment, you can file a bug report and include relevant output from that command to show the issue. See Running & Writing Tests for more on running tests.
--prefix argument to the configure
script) you must take care that your primary python executable is not
overwritten by the installation of a different version. All files and
directories installed using make altinstall contain the major and minor
version and can thus live side-by-side. make install also creates
${prefix}/bin/python3 which refers to ${prefix}/bin/pythonX.Y. If you
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
and make altinstall in the others.