### 導航
- [索引](../genindex.xhtml "總目錄")
- [模塊](../py-modindex.xhtml "Python 模塊索引") |
- [下一頁](debug.xhtml "調試和分析") |
- [上一頁](2to3.xhtml "2to3 - 自動將 Python 2 代碼轉為 Python 3 代碼") |
- 
- [Python](https://www.python.org/) ?
- zh\_CN 3.7.3 [文檔](../index.xhtml) ?
- [Python 標準庫](index.xhtml) ?
- [開發工具](development.xhtml) ?
- $('.inline-search').show(0); |
# [`test`](#module-test "test: Regression tests package containing the testing suite for Python.") --- Regression tests package for Python
注解
The [`test`](#module-test "test: Regression tests package containing the testing suite for Python.") package is meant for internal use by Python only. It is documented for the benefit of the core developers of Python. Any use of this package outside of Python's standard library is discouraged as code mentioned here can change or be removed without notice between releases of Python.
- - - - - -
The [`test`](#module-test "test: Regression tests package containing the testing suite for Python.") package contains all regression tests for Python as well as the modules [`test.support`](#module-test.support "test.support: Support for Python's regression test suite.") and `test.regrtest`. [`test.support`](#module-test.support "test.support: Support for Python's regression test suite.") is used to enhance your tests while `test.regrtest` drives the testing suite.
Each module in the [`test`](#module-test "test: Regression tests package containing the testing suite for Python.") package whose name starts with `test_` is a testing suite for a specific module or feature. All new tests should be written using the [`unittest`](unittest.xhtml#module-unittest "unittest: Unit testing framework for Python.") or [`doctest`](doctest.xhtml#module-doctest "doctest: Test pieces of code within docstrings.") module. Some older tests are written using a "traditional" testing style that compares output printed to `sys.stdout`; this style of test is considered deprecated.
參見
Module [`unittest`](unittest.xhtml#module-unittest "unittest: Unit testing framework for Python.")Writing PyUnit regression tests.
[`unittest`](unittest.xhtml#module-unittest "unittest: Unit testing framework for Python.") --- 文檔測試Tests embedded in documentation strings.
## Writing Unit Tests for the [`test`](#module-test "test: Regression tests package containing the testing suite for Python.") package
It is preferred that tests that use the [`unittest`](unittest.xhtml#module-unittest "unittest: Unit testing framework for Python.") module follow a few guidelines. One is to name the test module by starting it with `test_` and end it with the name of the module being tested. The test methods in the test module should start with `test_` and end with a description of what the method is testing. This is needed so that the methods are recognized by the test driver as test methods. Also, no documentation string for the method should be included. A comment (such as `# Tests function returns only True or False`) should be used to provide documentation for test methods. This is done because documentation strings get printed out if they exist and thus what test is being run is not stated.
A basic boilerplate is often used:
```
import unittest
from test import support
class MyTestCase1(unittest.TestCase):
# Only use setUp() and tearDown() if necessary
def setUp(self):
... code to execute in preparation for tests ...
def tearDown(self):
... code to execute to clean up after tests ...
def test_feature_one(self):
# Test feature one.
... testing code ...
def test_feature_two(self):
# Test feature two.
... testing code ...
... more test methods ...
class MyTestCase2(unittest.TestCase):
... same structure as MyTestCase1 ...
... more test classes ...
if __name__ == '__main__':
unittest.main()
```
This code pattern allows the testing suite to be run by `test.regrtest`, on its own as a script that supports the [`unittest`](unittest.xhtml#module-unittest "unittest: Unit testing framework for Python.") CLI, or via the `python -m unittest` CLI.
The goal for regression testing is to try to break code. This leads to a few guidelines to be followed:
- The testing suite should exercise all classes, functions, and constants. This includes not just the external API that is to be presented to the outside world but also "private" code.
- Whitebox testing (examining the code being tested when the tests are being written) is preferred. Blackbox testing (testing only the published user interface) is not complete enough to make sure all boundary and edge cases are tested.
- Make sure all possible values are tested including invalid ones. This makes sure that not only all valid values are acceptable but also that improper values are handled correctly.
- Exhaust as many code paths as possible. Test where branching occurs and thus tailor input to make sure as many different paths through the code are taken.
- Add an explicit test for any bugs discovered for the tested code. This will make sure that the error does not crop up again if the code is changed in the future.
- Make sure to clean up after your tests (such as close and remove all temporary files).
- If a test is dependent on a specific condition of the operating system then verify the condition already exists before attempting the test.
- Import as few modules as possible and do it as soon as possible. This minimizes external dependencies of tests and also minimizes possible anomalous behavior from side-effects of importing a module.
- Try to maximize code reuse. On occasion, tests will vary by something as small as what type of input is used. Minimize code duplication by subclassing a basic test class with a class that specifies the input:
```
class TestFuncAcceptsSequencesMixin:
func = mySuperWhammyFunction
def test_func(self):
self.func(self.arg)
class AcceptLists(TestFuncAcceptsSequencesMixin, unittest.TestCase):
arg = [1, 2, 3]
class AcceptStrings(TestFuncAcceptsSequencesMixin, unittest.TestCase):
arg = 'abc'
class AcceptTuples(TestFuncAcceptsSequencesMixin, unittest.TestCase):
arg = (1, 2, 3)
```
When using this pattern, remember that all classes that inherit from [`unittest.TestCase`](unittest.xhtml#unittest.TestCase "unittest.TestCase") are run as tests. The `Mixin` class in the example above does not have any data and so can't be run by itself, thus it does not inherit from [`unittest.TestCase`](unittest.xhtml#unittest.TestCase "unittest.TestCase").
參見
Test Driven DevelopmentA book by Kent Beck on writing tests before code.
## Running tests using the command-line interface
The [`test`](#module-test "test: Regression tests package containing the testing suite for Python.") package can be run as a script to drive Python's regression test suite, thanks to the [`-m`](../using/cmdline.xhtml#cmdoption-m) option: **python -m test**. Under the hood, it uses `test.regrtest`; the call **python -m test.regrtest** used in previous Python versions still works. Running the script by itself automatically starts running all regression tests in the [`test`](#module-test "test: Regression tests package containing the testing suite for Python.") package. It does this by finding all modules in the package whose name starts with `test_`, importing them, and executing the function `test_main()` if present or loading the tests via unittest.TestLoader.loadTestsFromModule if `test_main` does not exist. The names of tests to execute may also be passed to the script. Specifying a single regression test (**python -m test test\_spam**) will minimize output and only print whether the test passed or failed.
Running [`test`](#module-test "test: Regression tests package containing the testing suite for Python.") directly allows what resources are available for tests to use to be set. You do this by using the `-u` command-line option. Specifying `all` as the value for the `-u` option enables all possible resources: **python -m test -uall**. If all but one resource is desired (a more common case), a comma-separated list of resources that are not desired may be listed after `all`. The command **python -m test -uall,-audio,-largefile**will run [`test`](#module-test "test: Regression tests package containing the testing suite for Python.") with all resources except the `audio` and `largefile` resources. For a list of all resources and more command-line options, run **python -m test -h**.
Some other ways to execute the regression tests depend on what platform the tests are being executed on. On Unix, you can run **make test** at the top-level directory where Python was built. On Windows, executing **rt.bat** from your `PCbuild` directory will run all regression tests.
# [`test.support`](#module-test.support "test.support: Support for Python's regression test suite.") --- Utilities for the Python test suite
The [`test.support`](#module-test.support "test.support: Support for Python's regression test suite.") module provides support for Python's regression test suite.
注解
[`test.support`](#module-test.support "test.support: Support for Python's regression test suite.") is not a public module. It is documented here to help Python developers write tests. The API of this module is subject to change without backwards compatibility concerns between releases.
This module defines the following exceptions:
*exception* `test.support.``TestFailed`Exception to be raised when a test fails. This is deprecated in favor of [`unittest`](unittest.xhtml#module-unittest "unittest: Unit testing framework for Python.")-based tests and [`unittest.TestCase`](unittest.xhtml#unittest.TestCase "unittest.TestCase")'s assertion methods.
*exception* `test.support.``ResourceDenied`Subclass of [`unittest.SkipTest`](unittest.xhtml#unittest.SkipTest "unittest.SkipTest"). Raised when a resource (such as a network connection) is not available. Raised by the [`requires()`](#test.support.requires "test.support.requires")function.
The [`test.support`](#module-test.support "test.support: Support for Python's regression test suite.") module defines the following constants:
`test.support.``verbose``True` when verbose output is enabled. Should be checked when more detailed information is desired about a running test. *verbose* is set by `test.regrtest`.
`test.support.``is_jython``True` if the running interpreter is Jython.
`test.support.``is_android``True` if the system is Android.
`test.support.``unix_shell`Path for shell if not on Windows; otherwise `None`.
`test.support.``FS_NONASCII`A non-ASCII character encodable by [`os.fsencode()`](os.xhtml#os.fsencode "os.fsencode").
`test.support.``TESTFN`Set to a name that is safe to use as the name of a temporary file. Any temporary file that is created should be closed and unlinked (removed).
`test.support.``TESTFN_UNICODE`Set to a non-ASCII name for a temporary file.
`test.support.``TESTFN_ENCODING`Set to [`sys.getfilesystemencoding()`](sys.xhtml#sys.getfilesystemencoding "sys.getfilesystemencoding").
`test.support.``TESTFN_UNENCODABLE`Set to a filename (str type) that should not be able to be encoded by file system encoding in strict mode. It may be `None` if it's not possible to generate such a filename.
`test.support.``TESTFN_UNDECODABLE`Set to a filename (bytes type) that should not be able to be decoded by file system encoding in strict mode. It may be `None` if it's not possible to generate such a filename.
`test.support.``TESTFN_NONASCII`Set to a filename containing the [`FS_NONASCII`](#test.support.FS_NONASCII "test.support.FS_NONASCII") character.
`test.support.``IPV6_ENABLED`Set to `True` if IPV6 is enabled on this host, `False` otherwise.
`test.support.``SAVEDCWD`Set to [`os.getcwd()`](os.xhtml#os.getcwd "os.getcwd").
`test.support.``PGO`Set when tests can be skipped when they are not useful for PGO.
`test.support.``PIPE_MAX_SIZE`A constant that is likely larger than the underlying OS pipe buffer size, to make writes blocking.
`test.support.``SOCK_MAX_SIZE`A constant that is likely larger than the underlying OS socket buffer size, to make writes blocking.
`test.support.``TEST_SUPPORT_DIR`Set to the top level directory that contains [`test.support`](#module-test.support "test.support: Support for Python's regression test suite.").
`test.support.``TEST_HOME_DIR`Set to the top level directory for the test package.
`test.support.``TEST_DATA_DIR`Set to the `data` directory within the test package.
`test.support.``MAX_Py_ssize_t`Set to [`sys.maxsize`](sys.xhtml#sys.maxsize "sys.maxsize") for big memory tests.
`test.support.``max_memuse`Set by [`set_memlimit()`](#test.support.set_memlimit "test.support.set_memlimit") as the memory limit for big memory tests. Limited by [`MAX_Py_ssize_t`](#test.support.MAX_Py_ssize_t "test.support.MAX_Py_ssize_t").
`test.support.``real_max_memuse`Set by [`set_memlimit()`](#test.support.set_memlimit "test.support.set_memlimit") as the memory limit for big memory tests. Not limited by [`MAX_Py_ssize_t`](#test.support.MAX_Py_ssize_t "test.support.MAX_Py_ssize_t").
`test.support.``MISSING_C_DOCSTRINGS`Return `True` if running on CPython, not on Windows, and configuration not set with `WITH_DOC_STRINGS`.
`test.support.``HAVE_DOCSTRINGS`Check for presence of docstrings.
`test.support.``TEST_HTTP_URL`Define the URL of a dedicated HTTP server for the network tests.
The [`test.support`](#module-test.support "test.support: Support for Python's regression test suite.") module defines the following functions:
`test.support.``forget`(*module\_name*)Remove the module named *module\_name* from `sys.modules` and delete any byte-compiled files of the module.
`test.support.``unload`(*name*)Delete *name* from `sys.modules`.
`test.support.``unlink`(*filename*)Call [`os.unlink()`](os.xhtml#os.unlink "os.unlink") on *filename*. On Windows platforms, this is wrapped with a wait loop that checks for the existence fo the file.
`test.support.``rmdir`(*filename*)Call [`os.rmdir()`](os.xhtml#os.rmdir "os.rmdir") on *filename*. On Windows platforms, this is wrapped with a wait loop that checks for the existence of the file.
`test.support.``rmtree`(*path*)Call [`shutil.rmtree()`](shutil.xhtml#shutil.rmtree "shutil.rmtree") on *path* or call [`os.lstat()`](os.xhtml#os.lstat "os.lstat") and [`os.rmdir()`](os.xhtml#os.rmdir "os.rmdir") to remove a path and its contents. On Windows platforms, this is wrapped with a wait loop that checks for the existence of the files.
`test.support.``make_legacy_pyc`(*source*)Move a PEP 3147/488 pyc file to its legacy pyc location and return the file system path to the legacy pyc file. The *source* value is the file system path to the source file. It does not need to exist, however the PEP 3147/488 pyc file must exist.
`test.support.``is_resource_enabled`(*resource*)Return `True` if *resource* is enabled and available. The list of available resources is only set when `test.regrtest` is executing the tests.
`test.support.``python_is_optimized`()Return `True` if Python was not built with `-O0` or `-Og`.
`test.support.``with_pymalloc`()Return `_testcapi.WITH_PYMALLOC`.
`test.support.``requires`(*resource*, *msg=None*)Raise [`ResourceDenied`](#test.support.ResourceDenied "test.support.ResourceDenied") if *resource* is not available. *msg* is the argument to [`ResourceDenied`](#test.support.ResourceDenied "test.support.ResourceDenied") if it is raised. Always returns `True` if called by a function whose `__name__` is `'__main__'`. Used when tests are executed by `test.regrtest`.
`test.support.``system_must_validate_cert`(*f*)Raise [`unittest.SkipTest`](unittest.xhtml#unittest.SkipTest "unittest.SkipTest") on TLS certification validation failures.
`test.support.``sortdict`(*dict*)Return a repr of *dict* with keys sorted.
`test.support.``findfile`(*filename*, *subdir=None*)Return the path to the file named *filename*. If no match is found *filename* is returned. This does not equal a failure since it could be the path to the file.
Setting *subdir* indicates a relative path to use to find the file rather than looking directly in the path directories.
`test.support.``create_empty_file`(*filename*)Create an empty file with *filename*. If it already exists, truncate it.
`test.support.``fd_count`()Count the number of open file descriptors.
`test.support.``match_test`(*test*)Match *test* to patterns set in [`set_match_tests()`](#test.support.set_match_tests "test.support.set_match_tests").
`test.support.``set_match_tests`(*patterns*)Define match test with regular expression *patterns*.
`test.support.``run_unittest`(*\*classes*)Execute [`unittest.TestCase`](unittest.xhtml#unittest.TestCase "unittest.TestCase") subclasses passed to the function. The function scans the classes for methods starting with the prefix `test_`and executes the tests individually.
It is also legal to pass strings as parameters; these should be keys in `sys.modules`. Each associated module will be scanned by `unittest.TestLoader.loadTestsFromModule()`. This is usually seen in the following `test_main()` function:
```
def test_main():
support.run_unittest(__name__)
```
This will run all tests defined in the named module.
`test.support.``run_doctest`(*module*, *verbosity=None*, *optionflags=0*)Run [`doctest.testmod()`](doctest.xhtml#doctest.testmod "doctest.testmod") on the given *module*. Return `(failure_count, test_count)`.
If *verbosity* is `None`, [`doctest.testmod()`](doctest.xhtml#doctest.testmod "doctest.testmod") is run with verbosity set to [`verbose`](#test.support.verbose "test.support.verbose"). Otherwise, it is run with verbosity set to `None`. *optionflags* is passed as `optionflags` to [`doctest.testmod()`](doctest.xhtml#doctest.testmod "doctest.testmod").
`test.support.``setswitchinterval`(*interval*)Set the [`sys.setswitchinterval()`](sys.xhtml#sys.setswitchinterval "sys.setswitchinterval") to the given *interval*. Defines a minimum interval for Android systems to prevent the system from hanging.
`test.support.``check_impl_detail`(*\*\*guards*)Use this check to guard CPython's implementation-specific tests or to run them only on the implementations guarded by the arguments:
```
check_impl_detail() # Only on CPython (default).
check_impl_detail(jython=True) # Only on Jython.
check_impl_detail(cpython=False) # Everywhere except CPython.
```
`test.support.``check_warnings`(*\*filters*, *quiet=True*)A convenience wrapper for [`warnings.catch_warnings()`](warnings.xhtml#warnings.catch_warnings "warnings.catch_warnings") that makes it easier to test that a warning was correctly raised. It is approximately equivalent to calling `warnings.catch_warnings(record=True)` with [`warnings.simplefilter()`](warnings.xhtml#warnings.simplefilter "warnings.simplefilter") set to `always` and with the option to automatically validate the results that are recorded.
`check_warnings` accepts 2-tuples of the form
```
("message regexp",
WarningCategory)
```
as positional arguments. If one or more *filters* are provided, or if the optional keyword argument *quiet* is `False`, it checks to make sure the warnings are as expected: each specified filter must match at least one of the warnings raised by the enclosed code or the test fails, and if any warnings are raised that do not match any of the specified filters the test fails. To disable the first of these checks, set *quiet* to `True`.
If no arguments are specified, it defaults to:
```
check_warnings(("", Warning), quiet=True)
```
In this case all warnings are caught and no errors are raised.
On entry to the context manager, a `WarningRecorder` instance is returned. The underlying warnings list from [`catch_warnings()`](warnings.xhtml#warnings.catch_warnings "warnings.catch_warnings") is available via the recorder object's [`warnings`](warnings.xhtml#module-warnings "warnings: Issue warning messages and control their disposition.") attribute. As a convenience, the attributes of the object representing the most recent warning can also be accessed directly through the recorder object (see example below). If no warning has been raised, then any of the attributes that would otherwise be expected on an object representing a warning will return `None`.
The recorder object also has a `reset()` method, which clears the warnings list.
The context manager is designed to be used like this:
```
with check_warnings(("assertion is always true", SyntaxWarning),
("", UserWarning)):
exec('assert(False, "Hey!")')
warnings.warn(UserWarning("Hide me!"))
```
In this case if either warning was not raised, or some other warning was raised, [`check_warnings()`](#test.support.check_warnings "test.support.check_warnings") would raise an error.
When a test needs to look more deeply into the warnings, rather than just checking whether or not they occurred, code like this can be used:
```
with check_warnings(quiet=True) as w:
warnings.warn("foo")
assert str(w.args[0]) == "foo"
warnings.warn("bar")
assert str(w.args[0]) == "bar"
assert str(w.warnings[0].args[0]) == "foo"
assert str(w.warnings[1].args[0]) == "bar"
w.reset()
assert len(w.warnings) == 0
```
Here all warnings will be caught, and the test code tests the captured warnings directly.
在 3.2 版更改: New optional arguments *filters* and *quiet*.
`test.support.``check_no_resource_warning`(*testcase*)Context manager to check that no [`ResourceWarning`](exceptions.xhtml#ResourceWarning "ResourceWarning") was raised. You must remove the object which may emit [`ResourceWarning`](exceptions.xhtml#ResourceWarning "ResourceWarning") before the end of the context manager.
`test.support.``set_memlimit`(*limit*)Set the values for [`max_memuse`](#test.support.max_memuse "test.support.max_memuse") and [`real_max_memuse`](#test.support.real_max_memuse "test.support.real_max_memuse") for big memory tests.
`test.support.``record_original_stdout`(*stdout*)Store the value from *stdout*. It is meant to hold the stdout at the time the regrtest began.
`test.support.``get_original_stdout`()Return the original stdout set by [`record_original_stdout()`](#test.support.record_original_stdout "test.support.record_original_stdout") or `sys.stdout` if it's not set.
`test.support.``strip_python_strerr`(*stderr*)Strip the *stderr* of a Python process from potential debug output emitted by the interpreter. This will typically be run on the result of [`subprocess.Popen.communicate()`](subprocess.xhtml#subprocess.Popen.communicate "subprocess.Popen.communicate").
`test.support.``args_from_interpreter_flags`()Return a list of command line arguments reproducing the current settings in `sys.flags` and `sys.warnoptions`.
`test.support.``optim_args_from_interpreter_flags`()Return a list of command line arguments reproducing the current optimization settings in `sys.flags`.
`test.support.``captured_stdin`()`test.support.``captured_stdout`()`test.support.``captured_stderr`()A context managers that temporarily replaces the named stream with [`io.StringIO`](io.xhtml#io.StringIO "io.StringIO") object.
Example use with output streams:
```
with captured_stdout() as stdout, captured_stderr() as stderr:
print("hello")
print("error", file=sys.stderr)
assert stdout.getvalue() == "hello\n"
assert stderr.getvalue() == "error\n"
```
Example use with input stream:
```
with captured_stdin() as stdin:
stdin.write('hello\n')
stdin.seek(0)
# call test code that consumes from sys.stdin
captured = input()
self.assertEqual(captured, "hello")
```
`test.support.``temp_dir`(*path=None*, *quiet=False*)A context manager that creates a temporary directory at *path* and yields the directory.
If *path* is `None`, the temporary directory is created using [`tempfile.mkdtemp()`](tempfile.xhtml#tempfile.mkdtemp "tempfile.mkdtemp"). If *quiet* is `False`, the context manager raises an exception on error. Otherwise, if *path* is specified and cannot be created, only a warning is issued.
`test.support.``change_cwd`(*path*, *quiet=False*)A context manager that temporarily changes the current working directory to *path* and yields the directory.
If *quiet* is `False`, the context manager raises an exception on error. Otherwise, it issues only a warning and keeps the current working directory the same.
`test.support.``temp_cwd`(*name='tempcwd'*, *quiet=False*)A context manager that temporarily creates a new directory and changes the current working directory (CWD).
The context manager creates a temporary directory in the current directory with name *name* before temporarily changing the current working directory. If *name* is `None`, the temporary directory is created using [`tempfile.mkdtemp()`](tempfile.xhtml#tempfile.mkdtemp "tempfile.mkdtemp").
If *quiet* is `False` and it is not possible to create or change the CWD, an error is raised. Otherwise, only a warning is raised and the original CWD is used.
`test.support.``temp_umask`(*umask*)A context manager that temporarily sets the process umask.
`test.support.``transient_internet`(*resource\_name*, *\**, *timeout=30.0*, *errnos=()*)A context manager that raises [`ResourceDenied`](#test.support.ResourceDenied "test.support.ResourceDenied") when various issues with the internet connection manifest themselves as exceptions.
`test.support.``disable_faulthandler`()A context manager that replaces `sys.stderr` with `sys.__stderr__`.
`test.support.``gc_collect`()Force as many objects as possible to be collected. This is needed because timely deallocation is not guaranteed by the garbage collector. This means that `__del__` methods may be called later than expected and weakrefs may remain alive for longer than expected.
`test.support.``disable_gc`()A context manager that disables the garbage collector upon entry and reenables it upon exit.
`test.support.``swap_attr`(*obj*, *attr*, *new\_val*)Context manager to swap out an attribute with a new object.
用法:
```
with swap_attr(obj, "attr", 5):
...
```
This will set `obj.attr` to 5 for the duration of the `with` block, restoring the old value at the end of the block. If `attr` doesn't exist on `obj`, it will be created and then deleted at the end of the block.
The old value (or `None` if it doesn't exist) will be assigned to the target of the "as" clause, if there is one.
`test.support.``swap_item`(*obj*, *attr*, *new\_val*)Context manager to swap out an item with a new object.
用法:
```
with swap_item(obj, "item", 5):
...
```
This will set `obj["item"]` to 5 for the duration of the `with` block, restoring the old value at the end of the block. If `item` doesn't exist on `obj`, it will be created and then deleted at the end of the block.
The old value (or `None` if it doesn't exist) will be assigned to the target of the "as" clause, if there is one.
`test.support.``wait_threads_exit`(*timeout=60.0*)Context manager to wait until all threads created in the `with` statement exit.
`test.support.``start_threads`(*threads*, *unlock=None*)Context manager to start *threads*. It attempts to join the threads upon exit.
`test.support.``calcobjsize`(*fmt*)Return [`struct.calcsize()`](struct.xhtml#struct.calcsize "struct.calcsize") for `nP{fmt}0n` or, if `gettotalrefcount`exists, `2PnP{fmt}0P`.
`test.support.``calcvobjsize`(*fmt*)Return [`struct.calcsize()`](struct.xhtml#struct.calcsize "struct.calcsize") for `nPn{fmt}0n` or, if `gettotalrefcount`exists, `2PnPn{fmt}0P`.
`test.support.``checksizeof`(*test*, *o*, *size*)For testcase *test*, assert that the `sys.getsizeof` for *o* plus the GC header size equals *size*.
`test.support.``can_symlink`()Return `True` if the OS supports symbolic links, `False`otherwise.
`test.support.``can_xattr`()Return `True` if the OS supports xattr, `False`otherwise.
`@``test.support.``skip_unless_symlink`A decorator for running tests that require support for symbolic links.
`@``test.support.``skip_unless_xattr`A decorator for running tests that require support for xattr.
`@``test.support.``skip_unless_bind_unix_socket`A decorator for running tests that require a functional bind() for Unix sockets.
`@``test.support.``anticipate_failure`(*condition*)A decorator to conditionally mark tests with [`unittest.expectedFailure()`](unittest.xhtml#unittest.expectedFailure "unittest.expectedFailure"). Any use of this decorator should have an associated comment identifying the relevant tracker issue.
`@``test.support.``run_with_locale`(*catstr*, *\*locales*)A decorator for running a function in a different locale, correctly resetting it after it has finished. *catstr* is the locale category as a string (for example `"LC_ALL"`). The *locales* passed will be tried sequentially, and the first valid locale will be used.
`@``test.support.``run_with_tz`(*tz*)A decorator for running a function in a specific timezone, correctly resetting it after it has finished.
`@``test.support.``requires_freebsd_version`(*\*min\_version*)Decorator for the minimum version when running test on FreeBSD. If the FreeBSD version is less than the minimum, raise [`unittest.SkipTest`](unittest.xhtml#unittest.SkipTest "unittest.SkipTest").
`@``test.support.``requires_linux_version`(*\*min\_version*)Decorator for the minimum version when running test on Linux. If the Linux version is less than the minimum, raise [`unittest.SkipTest`](unittest.xhtml#unittest.SkipTest "unittest.SkipTest").
`@``test.support.``requires_mac_version`(*\*min\_version*)Decorator for the minimum version when running test on Mac OS X. If the MAC OS X version is less than the minimum, raise [`unittest.SkipTest`](unittest.xhtml#unittest.SkipTest "unittest.SkipTest").
`@``test.support.``requires_IEEE_754`Decorator for skipping tests on non-IEEE 754 platforms.
`@``test.support.``requires_zlib`Decorator for skipping tests if [`zlib`](zlib.xhtml#module-zlib "zlib: Low-level interface to compression and decompression routines compatible with gzip.") doesn't exist.
`@``test.support.``requires_gzip`Decorator for skipping tests if [`gzip`](gzip.xhtml#module-gzip "gzip: Interfaces for gzip compression and decompression using file objects.") doesn't exist.
`@``test.support.``requires_bz2`Decorator for skipping tests if [`bz2`](bz2.xhtml#module-bz2 "bz2: Interfaces for bzip2 compression and decompression.") doesn't exist.
`@``test.support.``requires_lzma`Decorator for skipping tests if [`lzma`](lzma.xhtml#module-lzma "lzma: A Python wrapper for the liblzma compression library.") doesn't exist.
`@``test.support.``requires_resource`(*resource*)Decorator for skipping tests if *resource* is not available.
`@``test.support.``requires_docstrings`Decorator for only running the test if [`HAVE_DOCSTRINGS`](#test.support.HAVE_DOCSTRINGS "test.support.HAVE_DOCSTRINGS").
`@``test.support.``cpython_only`(*test*)Decorator for tests only applicable to CPython.
`@``test.support.``impl_detail`(*msg=None*, *\*\*guards*)Decorator for invoking [`check_impl_detail()`](#test.support.check_impl_detail "test.support.check_impl_detail") on *guards*. If that returns `False`, then uses *msg* as the reason for skipping the test.
`@``test.support.``no_tracing`(*func*)Decorator to temporarily turn off tracing for the duration of the test.
`@``test.support.``refcount_test`(*test*)Decorator for tests which involve reference counting. The decorator does not run the test if it is not run by CPython. Any trace function is unset for the duration of the test to prevent unexpected refcounts caused by the trace function.
`@``test.support.``reap_threads`(*func*)Decorator to ensure the threads are cleaned up even if the test fails.
`@``test.support.``bigmemtest`(*size*, *memuse*, *dry\_run=True*)Decorator for bigmem tests.
*size* is a requested size for the test (in arbitrary, test-interpreted units.) *memuse* is the number of bytes per unit for the test, or a good estimate of it. For example, a test that needs two byte buffers, of 4 GiB each, could be decorated with `@bigmemtest(size=_4G, memuse=2)`.
The *size* argument is normally passed to the decorated test method as an extra argument. If *dry\_run* is `True`, the value passed to the test method may be less than the requested value. If *dry\_run* is `False`, it means the test doesn't support dummy runs when `-M` is not specified.
`@``test.support.``bigaddrspacetest`(*f*)Decorator for tests that fill the address space. *f* is the function to wrap.
`test.support.``make_bad_fd`()Create an invalid file descriptor by opening and closing a temporary file, and returning its descriptor.
`test.support.``check_syntax_error`(*testcase*, *statement*, *errtext=''*, *\**, *lineno=None*, *offset=None*)Test for syntax errors in *statement* by attempting to compile *statement*. *testcase* is the [`unittest`](unittest.xhtml#module-unittest "unittest: Unit testing framework for Python.") instance for the test. *errtext* is the text of the error raised by [`SyntaxError`](exceptions.xhtml#SyntaxError "SyntaxError"). If *lineno* is not None, compares to the line of the [`SyntaxError`](exceptions.xhtml#SyntaxError "SyntaxError"). If *offset* is not None, compares to the offset of the [`SyntaxError`](exceptions.xhtml#SyntaxError "SyntaxError").
`test.support.``open_urlresource`(*url*, *\*args*, *\*\*kw*)Open *url*. If open fails, raises [`TestFailed`](#test.support.TestFailed "test.support.TestFailed").
`test.support.``import_module`(*name*, *deprecated=False*, *\**, *required\_on()*)This function imports and returns the named module. Unlike a normal import, this function raises [`unittest.SkipTest`](unittest.xhtml#unittest.SkipTest "unittest.SkipTest") if the module cannot be imported.
Module and package deprecation messages are suppressed during this import if *deprecated* is `True`. If a module is required on a platform but optional for others, set *required\_on* to an iterable of platform prefixes which will be compared against [`sys.platform`](sys.xhtml#sys.platform "sys.platform").
3\.1 新版功能.
`test.support.``import_fresh_module`(*name*, *fresh=()*, *blocked=()*, *deprecated=False*)This function imports and returns a fresh copy of the named Python module by removing the named module from `sys.modules` before doing the import. Note that unlike `reload()`, the original module is not affected by this operation.
*fresh* is an iterable of additional module names that are also removed from the `sys.modules` cache before doing the import.
*blocked* is an iterable of module names that are replaced with `None`in the module cache during the import to ensure that attempts to import them raise [`ImportError`](exceptions.xhtml#ImportError "ImportError").
The named module and any modules named in the *fresh* and *blocked*parameters are saved before starting the import and then reinserted into `sys.modules` when the fresh import is complete.
Module and package deprecation messages are suppressed during this import if *deprecated* is `True`.
This function will raise [`ImportError`](exceptions.xhtml#ImportError "ImportError") if the named module cannot be imported.
Example use:
```
# Get copies of the warnings module for testing without affecting the
# version being used by the rest of the test suite. One copy uses the
# C implementation, the other is forced to use the pure Python fallback
# implementation
py_warnings = import_fresh_module('warnings', blocked=['_warnings'])
c_warnings = import_fresh_module('warnings', fresh=['_warnings'])
```
3\.1 新版功能.
`test.support.``modules_setup`()Return a copy of [`sys.modules`](sys.xhtml#sys.modules "sys.modules").
`test.support.``modules_cleanup`(*oldmodules*)Remove modules except for *oldmodules* and `encodings` in order to preserve internal cache.
`test.support.``threading_setup`()Return current thread count and copy of dangling threads.
`test.support.``threading_cleanup`(*\*original\_values*)Cleanup up threads not specified in *original\_values*. Designed to emit a warning if a test leaves running threads in the background.
`test.support.``join_thread`(*thread*, *timeout=30.0*)Join a *thread* within *timeout*. Raise an [`AssertionError`](exceptions.xhtml#AssertionError "AssertionError") if thread is still alive after *timeout* seconds.
`test.support.``reap_children`()Use this at the end of `test_main` whenever sub-processes are started. This will help ensure that no extra children (zombies) stick around to hog resources and create problems when looking for refleaks.
`test.support.``get_attribute`(*obj*, *name*)Get an attribute, raising [`unittest.SkipTest`](unittest.xhtml#unittest.SkipTest "unittest.SkipTest") if [`AttributeError`](exceptions.xhtml#AttributeError "AttributeError")is raised.
`test.support.``bind_port`(*sock*, *host=HOST*)Bind the socket to a free port and return the port number. Relies on ephemeral ports in order to ensure we are using an unbound port. This is important as many tests may be running simultaneously, especially in a buildbot environment. This method raises an exception if the `sock.family` is [`AF_INET`](socket.xhtml#socket.AF_INET "socket.AF_INET") and `sock.type` is [`SOCK_STREAM`](socket.xhtml#socket.SOCK_STREAM "socket.SOCK_STREAM"), and the socket has `SO_REUSEADDR` or `SO_REUSEPORT` set on it. Tests should never set these socket options for TCP/IP sockets. The only case for setting these options is testing multicasting via multiple UDP sockets.
Additionally, if the `SO_EXCLUSIVEADDRUSE` socket option is available (i.e. on Windows), it will be set on the socket. This will prevent anyone else from binding to our host/port for the duration of the test.
`test.support.``bind_unix_socket`(*sock*, *addr*)Bind a unix socket, raising [`unittest.SkipTest`](unittest.xhtml#unittest.SkipTest "unittest.SkipTest") if [`PermissionError`](exceptions.xhtml#PermissionError "PermissionError") is raised.
`test.support.``find_unused_port`(*family=socket.AF\_INET*, *socktype=socket.SOCK\_STREAM*)Returns an unused port that should be suitable for binding. This is achieved by creating a temporary socket with the same family and type as the `sock` parameter (default is [`AF_INET`](socket.xhtml#socket.AF_INET "socket.AF_INET"), [`SOCK_STREAM`](socket.xhtml#socket.SOCK_STREAM "socket.SOCK_STREAM")), and binding it to the specified host address (defaults to `0.0.0.0`) with the port set to 0, eliciting an unused ephemeral port from the OS. The temporary socket is then closed and deleted, and the ephemeral port is returned.
Either this method or [`bind_port()`](#test.support.bind_port "test.support.bind_port") should be used for any tests where a server socket needs to be bound to a particular port for the duration of the test. Which one to use depends on whether the calling code is creating a Python socket, or if an unused port needs to be provided in a constructor or passed to an external program (i.e. the `-accept` argument to openssl's s\_server mode). Always prefer [`bind_port()`](#test.support.bind_port "test.support.bind_port") over [`find_unused_port()`](#test.support.find_unused_port "test.support.find_unused_port") where possible. Using a hard coded port is discouraged since it can make multiple instances of the test impossible to run simultaneously, which is a problem for buildbots.
`test.support.``load_package_tests`(*pkg\_dir*, *loader*, *standard\_tests*, *pattern*)Generic implementation of the [`unittest`](unittest.xhtml#module-unittest "unittest: Unit testing framework for Python.")`load_tests` protocol for use in test packages. *pkg\_dir* is the root directory of the package; *loader*, *standard\_tests*, and *pattern* are the arguments expected by `load_tests`. In simple cases, the test package's `__init__.py`can be the following:
```
import os
from test.support import load_package_tests
def load_tests(*args):
return load_package_tests(os.path.dirname(__file__), *args)
```
`test.support.``fs_is_case_insensitive`(*directory*)Return `True` if the file system for *directory* is case-insensitive.
`test.support.``detect_api_mismatch`(*ref\_api*, *other\_api*, *\**, *ignore=()*)Returns the set of attributes, functions or methods of *ref\_api* not found on *other\_api*, except for a defined list of items to be ignored in this check specified in *ignore*.
By default this skips private attributes beginning with '\_' but includes all magic methods, i.e. those starting and ending in '\_\_'.
3\.5 新版功能.
`test.support.``patch`(*test\_instance*, *object\_to\_patch*, *attr\_name*, *new\_value*)Override *object\_to\_patch.attr\_name* with *new\_value*. Also add cleanup procedure to *test\_instance* to restore *object\_to\_patch* for *attr\_name*. The *attr\_name* should be a valid attribute for *object\_to\_patch*.
`test.support.``run_in_subinterp`(*code*)Run *code* in subinterpreter. Raise [`unittest.SkipTest`](unittest.xhtml#unittest.SkipTest "unittest.SkipTest") if [`tracemalloc`](tracemalloc.xhtml#module-tracemalloc "tracemalloc: Trace memory allocations.") is enabled.
`test.support.``check_free_after_iterating`(*test*, *iter*, *cls*, *args=()*)Assert that *iter* is deallocated after iterating.
`test.support.``missing_compiler_executable`(*cmd\_names=\[\]*)Check for the existence of the compiler executables whose names are listed in *cmd\_names* or all the compiler executables when *cmd\_names* is empty and return the first missing executable or `None` when none is found missing.
`test.support.``check__all__`(*test\_case*, *module*, *name\_of\_module=None*, *extra=()*, *blacklist=()*)Assert that the `__all__` variable of *module* contains all public names.
The module's public names (its API) are detected automatically based on whether they match the public name convention and were defined in *module*.
The *name\_of\_module* argument can specify (as a string or tuple thereof) what module(s) an API could be defined in order to be detected as a public API. One case for this is when *module* imports part of its public API from other modules, possibly a C backend (like `csv` and its `_csv`).
The *extra* argument can be a set of names that wouldn't otherwise be automatically detected as "public", like objects without a proper `__module__`attribute. If provided, it will be added to the automatically detected ones.
The *blacklist* argument can be a set of names that must not be treated as part of the public API even though their names indicate otherwise.
Example use:
```
import bar
import foo
import unittest
from test import support
class MiscTestCase(unittest.TestCase):
def test__all__(self):
support.check__all__(self, foo)
class OtherTestCase(unittest.TestCase):
def test__all__(self):
extra = {'BAR_CONST', 'FOO_CONST'}
blacklist = {'baz'} # Undocumented name.
# bar imports part of its API from _bar.
support.check__all__(self, bar, ('bar', '_bar'),
extra=extra, blacklist=blacklist)
```
3\.6 新版功能.
The [`test.support`](#module-test.support "test.support: Support for Python's regression test suite.") module defines the following classes:
*class* `test.support.``TransientResource`(*exc*, *\*\*kwargs*)Instances are a context manager that raises [`ResourceDenied`](#test.support.ResourceDenied "test.support.ResourceDenied") if the specified exception type is raised. Any keyword arguments are treated as attribute/value pairs to be compared against any exception raised within the [`with`](../reference/compound_stmts.xhtml#with) statement. Only if all pairs match properly against attributes on the exception is [`ResourceDenied`](#test.support.ResourceDenied "test.support.ResourceDenied") raised.
*class* `test.support.``EnvironmentVarGuard`Class used to temporarily set or unset environment variables. Instances can be used as a context manager and have a complete dictionary interface for querying/modifying the underlying `os.environ`. After exit from the context manager all changes to environment variables done through this instance will be rolled back.
在 3.1 版更改: Added dictionary interface.
`EnvironmentVarGuard.``set`(*envvar*, *value*)Temporarily set the environment variable `envvar` to the value of `value`.
`EnvironmentVarGuard.``unset`(*envvar*)Temporarily unset the environment variable `envvar`.
*class* `test.support.``SuppressCrashReport`A context manager used to try to prevent crash dialog popups on tests that are expected to crash a subprocess.
On Windows, it disables Windows Error Reporting dialogs using [SetErrorMode](https://msdn.microsoft.com/en-us/library/windows/desktop/ms680621.aspx) \[https://msdn.microsoft.com/en-us/library/windows/desktop/ms680621.aspx\].
On UNIX, [`resource.setrlimit()`](resource.xhtml#resource.setrlimit "resource.setrlimit") is used to set [`resource.RLIMIT_CORE`](resource.xhtml#resource.RLIMIT_CORE "resource.RLIMIT_CORE")'s soft limit to 0 to prevent coredump file creation.
On both platforms, the old value is restored by [`__exit__()`](../reference/datamodel.xhtml#object.__exit__ "object.__exit__").
*class* `test.support.``CleanImport`(*\*module\_names*)A context manager to force import to return a new module reference. This is useful for testing module-level behaviors, such as the emission of a DeprecationWarning on import. Example usage:
```
with CleanImport('foo'):
importlib.import_module('foo') # New reference.
```
*class* `test.support.``DirsOnSysPath`(*\*paths*)A context manager to temporarily add directories to sys.path.
This makes a copy of [`sys.path`](sys.xhtml#sys.path "sys.path"), appends any directories given as positional arguments, then reverts [`sys.path`](sys.xhtml#sys.path "sys.path") to the copied settings when the context ends.
Note that *all* [`sys.path`](sys.xhtml#sys.path "sys.path") modifications in the body of the context manager, including replacement of the object, will be reverted at the end of the block.
*class* `test.support.``SaveSignals`Class to save and restore signal handlers registered by the Python signal handler.
*class* `test.support.``Matcher``matches`(*self*, *d*, *\*\*kwargs*)Try to match a single dict with the supplied arguments.
`match_value`(*self*, *k*, *dv*, *v*)Try to match a single stored value (*dv*) with a supplied value (*v*).
*class* `test.support.``WarningsRecorder`Class used to record warnings for unit tests. See documentation of [`check_warnings()`](#test.support.check_warnings "test.support.check_warnings") above for more details.
*class* `test.support.``BasicTestRunner``run`(*test*)Run *test* and return the result.
*class* `test.support.``TestHandler`(*logging.handlers.BufferingHandler*)Class for logging support.
*class* `test.support.``FakePath`(*path*)Simple [path-like object](../glossary.xhtml#term-path-like-object). It implements the `__fspath__()`method which just returns the *path* argument. If *path* is an exception, it will be raised in `__fspath__()`.
# [`test.support.script_helper`](#module-test.support.script_helper "test.support.script_helper: Support for Python's script execution tests.") --- Utilities for the Python execution tests
The [`test.support.script_helper`](#module-test.support.script_helper "test.support.script_helper: Support for Python's script execution tests.") module provides support for Python's script execution tests.
`test.support.script_helper.``interpreter_requires_environment`()Return `True` if `sys.executable interpreter` requires environment variables in order to be able to run at all.
This is designed to be used with `@unittest.skipIf()` to annotate tests that need to use an `assert_python*()` function to launch an isolated mode (`-I`) or no environment mode (`-E`) sub-interpreter process.
A normal build & test does not run into this situation but it can happen when trying to run the standard library test suite from an interpreter that doesn't have an obvious home with Python's current home finding logic.
Setting [`PYTHONHOME`](../using/cmdline.xhtml#envvar-PYTHONHOME) is one way to get most of the testsuite to run in that situation. [`PYTHONPATH`](../using/cmdline.xhtml#envvar-PYTHONPATH) or `PYTHONUSERSITE` are other common environment variables that might impact whether or not the interpreter can start.
`test.support.script_helper.``run_python_until_end`(*\*args*, *\*\*env\_vars*)Set up the environment based on *env\_vars* for running the interpreter in a subprocess. The values can include `__isolated`, `__cleanenv`, `__cwd`, and `TERM`.
`test.support.script_helper.``assert_python_ok`(*\*args*, *\*\*env\_vars*)Assert that running the interpreter with *args* and optional environment variables *env\_vars* succeeds (`rc == 0`) and return a
```
(return code,
stdout, stderr)
```
tuple.
If the `__cleanenv` keyword is set, *env\_vars* is used as a fresh environment.
Python is started in isolated mode (command line option `-I`), except if the `__isolated` keyword is set to `False`.
`test.support.script_helper.``assert_python_failure`(*\*args*, *\*\*env\_vars*)Assert that running the interpreter with *args* and optional environment variables *env\_vars* fails (`rc != 0`) and return a
```
(return code,
stdout, stderr)
```
tuple.
See [`assert_python_ok()`](#test.support.script_helper.assert_python_ok "test.support.script_helper.assert_python_ok") for more options.
`test.support.script_helper.``spawn_python`(*\*args*, *stdout=subprocess.PIPE*, *stderr=subprocess.STDOUT*, *\*\*kw*)Run a Python subprocess with the given arguments.
*kw* is extra keyword args to pass to [`subprocess.Popen()`](subprocess.xhtml#subprocess.Popen "subprocess.Popen"). Returns a [`subprocess.Popen`](subprocess.xhtml#subprocess.Popen "subprocess.Popen") object.
`test.support.script_helper.``kill_python`(*p*)Run the given [`subprocess.Popen`](subprocess.xhtml#subprocess.Popen "subprocess.Popen") process until completion and return stdout.
`test.support.script_helper.``make_script`(*script\_dir*, *script\_basename*, *source*, *omit\_suffix=False*)Create script containing *source* in path *script\_dir* and *script\_basename*. If *omit\_suffix* is `False`, append `.py` to the name. Return the full script path.
`test.support.script_helper.``make_zip_script`(*zip\_dir*, *zip\_basename*, *script\_name*, *name\_in\_zip=None*)Create zip file at *zip\_dir* and *zip\_basename* with extension `zip` which contains the files in *script\_name*. *name\_in\_zip* is the archive name. Return a tuple containing `(full path, full path of archive name)`.
`test.support.script_helper.``make_pkg`(*pkg\_dir*, *init\_source=''*)Create a directory named *pkg\_dir* containing an `__init__` file with *init\_source* as its contents.
`test.support.script_helper.``make_zip_pkg`(*zip\_dir*, *zip\_basename*, *pkg\_name*, *script\_basename*, *source*, *depth=1*, *compiled=False*)Create a zip package directory with a path of *zip\_dir* and *zip\_basename*containing an empty `__init__` file and a file *script\_basename*containing the *source*. If *compiled* is `True`, both source files will be compiled and added to the zip package. Return a tuple of the full zip path and the archive name for the zip file.
### 導航
- [索引](../genindex.xhtml "總目錄")
- [模塊](../py-modindex.xhtml "Python 模塊索引") |
- [下一頁](debug.xhtml "調試和分析") |
- [上一頁](2to3.xhtml "2to3 - 自動將 Python 2 代碼轉為 Python 3 代碼") |
- 
- [Python](https://www.python.org/) ?
- zh\_CN 3.7.3 [文檔](../index.xhtml) ?
- [Python 標準庫](index.xhtml) ?
- [開發工具](development.xhtml) ?
- $('.inline-search').show(0); |
? [版權所有](../copyright.xhtml) 2001-2019, Python Software Foundation.
Python 軟件基金會是一個非盈利組織。 [請捐助。](https://www.python.org/psf/donations/)
最后更新于 5月 21, 2019. [發現了問題](../bugs.xhtml)?
使用[Sphinx](http://sphinx.pocoo.org/)1.8.4 創建。
- Python文檔內容
- Python 有什么新變化?
- Python 3.7 有什么新變化
- 摘要 - 發布重點
- 新的特性
- 其他語言特性修改
- 新增模塊
- 改進的模塊
- C API 的改變
- 構建的改變
- 性能優化
- 其他 CPython 實現的改變
- 已棄用的 Python 行為
- 已棄用的 Python 模塊、函數和方法
- 已棄用的 C API 函數和類型
- 平臺支持的移除
- API 與特性的移除
- 移除的模塊
- Windows 專屬的改變
- 移植到 Python 3.7
- Python 3.7.1 中的重要變化
- Python 3.7.2 中的重要變化
- Python 3.6 有什么新變化A
- 摘要 - 發布重點
- 新的特性
- 其他語言特性修改
- 新增模塊
- 改進的模塊
- 性能優化
- Build and C API Changes
- 其他改進
- 棄用
- 移除
- 移植到Python 3.6
- Python 3.6.2 中的重要變化
- Python 3.6.4 中的重要變化
- Python 3.6.5 中的重要變化
- Python 3.6.7 中的重要變化
- Python 3.5 有什么新變化
- 摘要 - 發布重點
- 新的特性
- 其他語言特性修改
- 新增模塊
- 改進的模塊
- Other module-level changes
- 性能優化
- Build and C API Changes
- 棄用
- 移除
- Porting to Python 3.5
- Notable changes in Python 3.5.4
- What's New In Python 3.4
- 摘要 - 發布重點
- 新的特性
- 新增模塊
- 改進的模塊
- CPython Implementation Changes
- 棄用
- 移除
- Porting to Python 3.4
- Changed in 3.4.3
- What's New In Python 3.3
- 摘要 - 發布重點
- PEP 405: Virtual Environments
- PEP 420: Implicit Namespace Packages
- PEP 3118: New memoryview implementation and buffer protocol documentation
- PEP 393: Flexible String Representation
- PEP 397: Python Launcher for Windows
- PEP 3151: Reworking the OS and IO exception hierarchy
- PEP 380: Syntax for Delegating to a Subgenerator
- PEP 409: Suppressing exception context
- PEP 414: Explicit Unicode literals
- PEP 3155: Qualified name for classes and functions
- PEP 412: Key-Sharing Dictionary
- PEP 362: Function Signature Object
- PEP 421: Adding sys.implementation
- Using importlib as the Implementation of Import
- 其他語言特性修改
- A Finer-Grained Import Lock
- Builtin functions and types
- 新增模塊
- 改進的模塊
- 性能優化
- Build and C API Changes
- 棄用
- Porting to Python 3.3
- What's New In Python 3.2
- PEP 384: Defining a Stable ABI
- PEP 389: Argparse Command Line Parsing Module
- PEP 391: Dictionary Based Configuration for Logging
- PEP 3148: The concurrent.futures module
- PEP 3147: PYC Repository Directories
- PEP 3149: ABI Version Tagged .so Files
- PEP 3333: Python Web Server Gateway Interface v1.0.1
- 其他語言特性修改
- New, Improved, and Deprecated Modules
- 多線程
- 性能優化
- Unicode
- Codecs
- 文檔
- IDLE
- Code Repository
- Build and C API Changes
- Porting to Python 3.2
- What's New In Python 3.1
- PEP 372: Ordered Dictionaries
- PEP 378: Format Specifier for Thousands Separator
- 其他語言特性修改
- New, Improved, and Deprecated Modules
- 性能優化
- IDLE
- Build and C API Changes
- Porting to Python 3.1
- What's New In Python 3.0
- Common Stumbling Blocks
- Overview Of Syntax Changes
- Changes Already Present In Python 2.6
- Library Changes
- PEP 3101: A New Approach To String Formatting
- Changes To Exceptions
- Miscellaneous Other Changes
- Build and C API Changes
- 性能
- Porting To Python 3.0
- What's New in Python 2.7
- The Future for Python 2.x
- Changes to the Handling of Deprecation Warnings
- Python 3.1 Features
- PEP 372: Adding an Ordered Dictionary to collections
- PEP 378: Format Specifier for Thousands Separator
- PEP 389: The argparse Module for Parsing Command Lines
- PEP 391: Dictionary-Based Configuration For Logging
- PEP 3106: Dictionary Views
- PEP 3137: The memoryview Object
- 其他語言特性修改
- New and Improved Modules
- Build and C API Changes
- Other Changes and Fixes
- Porting to Python 2.7
- New Features Added to Python 2.7 Maintenance Releases
- Acknowledgements
- Python 2.6 有什么新變化
- Python 3.0
- Changes to the Development Process
- PEP 343: The 'with' statement
- PEP 366: Explicit Relative Imports From a Main Module
- PEP 370: Per-user site-packages Directory
- PEP 371: The multiprocessing Package
- PEP 3101: Advanced String Formatting
- PEP 3105: print As a Function
- PEP 3110: Exception-Handling Changes
- PEP 3112: Byte Literals
- PEP 3116: New I/O Library
- PEP 3118: Revised Buffer Protocol
- PEP 3119: Abstract Base Classes
- PEP 3127: Integer Literal Support and Syntax
- PEP 3129: Class Decorators
- PEP 3141: A Type Hierarchy for Numbers
- 其他語言特性修改
- New and Improved Modules
- Deprecations and Removals
- Build and C API Changes
- Porting to Python 2.6
- Acknowledgements
- What's New in Python 2.5
- PEP 308: Conditional Expressions
- PEP 309: Partial Function Application
- PEP 314: Metadata for Python Software Packages v1.1
- PEP 328: Absolute and Relative Imports
- PEP 338: Executing Modules as Scripts
- PEP 341: Unified try/except/finally
- PEP 342: New Generator Features
- PEP 343: The 'with' statement
- PEP 352: Exceptions as New-Style Classes
- PEP 353: Using ssize_t as the index type
- PEP 357: The 'index' method
- 其他語言特性修改
- New, Improved, and Removed Modules
- Build and C API Changes
- Porting to Python 2.5
- Acknowledgements
- What's New in Python 2.4
- PEP 218: Built-In Set Objects
- PEP 237: Unifying Long Integers and Integers
- PEP 289: Generator Expressions
- PEP 292: Simpler String Substitutions
- PEP 318: Decorators for Functions and Methods
- PEP 322: Reverse Iteration
- PEP 324: New subprocess Module
- PEP 327: Decimal Data Type
- PEP 328: Multi-line Imports
- PEP 331: Locale-Independent Float/String Conversions
- 其他語言特性修改
- New, Improved, and Deprecated Modules
- Build and C API Changes
- Porting to Python 2.4
- Acknowledgements
- What's New in Python 2.3
- PEP 218: A Standard Set Datatype
- PEP 255: Simple Generators
- PEP 263: Source Code Encodings
- PEP 273: Importing Modules from ZIP Archives
- PEP 277: Unicode file name support for Windows NT
- PEP 278: Universal Newline Support
- PEP 279: enumerate()
- PEP 282: The logging Package
- PEP 285: A Boolean Type
- PEP 293: Codec Error Handling Callbacks
- PEP 301: Package Index and Metadata for Distutils
- PEP 302: New Import Hooks
- PEP 305: Comma-separated Files
- PEP 307: Pickle Enhancements
- Extended Slices
- 其他語言特性修改
- New, Improved, and Deprecated Modules
- Pymalloc: A Specialized Object Allocator
- Build and C API Changes
- Other Changes and Fixes
- Porting to Python 2.3
- Acknowledgements
- What's New in Python 2.2
- 概述
- PEPs 252 and 253: Type and Class Changes
- PEP 234: Iterators
- PEP 255: Simple Generators
- PEP 237: Unifying Long Integers and Integers
- PEP 238: Changing the Division Operator
- Unicode Changes
- PEP 227: Nested Scopes
- New and Improved Modules
- Interpreter Changes and Fixes
- Other Changes and Fixes
- Acknowledgements
- What's New in Python 2.1
- 概述
- PEP 227: Nested Scopes
- PEP 236: future Directives
- PEP 207: Rich Comparisons
- PEP 230: Warning Framework
- PEP 229: New Build System
- PEP 205: Weak References
- PEP 232: Function Attributes
- PEP 235: Importing Modules on Case-Insensitive Platforms
- PEP 217: Interactive Display Hook
- PEP 208: New Coercion Model
- PEP 241: Metadata in Python Packages
- New and Improved Modules
- Other Changes and Fixes
- Acknowledgements
- What's New in Python 2.0
- 概述
- What About Python 1.6?
- New Development Process
- Unicode
- 列表推導式
- Augmented Assignment
- 字符串的方法
- Garbage Collection of Cycles
- Other Core Changes
- Porting to 2.0
- Extending/Embedding Changes
- Distutils: Making Modules Easy to Install
- XML Modules
- Module changes
- New modules
- IDLE Improvements
- Deleted and Deprecated Modules
- Acknowledgements
- 更新日志
- Python 下一版
- Python 3.7.3 最終版
- Python 3.7.3 發布候選版 1
- Python 3.7.2 最終版
- Python 3.7.2 發布候選版 1
- Python 3.7.1 最終版
- Python 3.7.1 RC 2版本
- Python 3.7.1 發布候選版 1
- Python 3.7.0 正式版
- Python 3.7.0 release candidate 1
- Python 3.7.0 beta 5
- Python 3.7.0 beta 4
- Python 3.7.0 beta 3
- Python 3.7.0 beta 2
- Python 3.7.0 beta 1
- Python 3.7.0 alpha 4
- Python 3.7.0 alpha 3
- Python 3.7.0 alpha 2
- Python 3.7.0 alpha 1
- Python 3.6.6 final
- Python 3.6.6 RC 1
- Python 3.6.5 final
- Python 3.6.5 release candidate 1
- Python 3.6.4 final
- Python 3.6.4 release candidate 1
- Python 3.6.3 final
- Python 3.6.3 release candidate 1
- Python 3.6.2 final
- Python 3.6.2 release candidate 2
- Python 3.6.2 release candidate 1
- Python 3.6.1 final
- Python 3.6.1 release candidate 1
- Python 3.6.0 final
- Python 3.6.0 release candidate 2
- Python 3.6.0 release candidate 1
- Python 3.6.0 beta 4
- Python 3.6.0 beta 3
- Python 3.6.0 beta 2
- Python 3.6.0 beta 1
- Python 3.6.0 alpha 4
- Python 3.6.0 alpha 3
- Python 3.6.0 alpha 2
- Python 3.6.0 alpha 1
- Python 3.5.5 final
- Python 3.5.5 release candidate 1
- Python 3.5.4 final
- Python 3.5.4 release candidate 1
- Python 3.5.3 final
- Python 3.5.3 release candidate 1
- Python 3.5.2 final
- Python 3.5.2 release candidate 1
- Python 3.5.1 final
- Python 3.5.1 release candidate 1
- Python 3.5.0 final
- Python 3.5.0 release candidate 4
- Python 3.5.0 release candidate 3
- Python 3.5.0 release candidate 2
- Python 3.5.0 release candidate 1
- Python 3.5.0 beta 4
- Python 3.5.0 beta 3
- Python 3.5.0 beta 2
- Python 3.5.0 beta 1
- Python 3.5.0 alpha 4
- Python 3.5.0 alpha 3
- Python 3.5.0 alpha 2
- Python 3.5.0 alpha 1
- Python 教程
- 課前甜點
- 使用 Python 解釋器
- 調用解釋器
- 解釋器的運行環境
- Python 的非正式介紹
- Python 作為計算器使用
- 走向編程的第一步
- 其他流程控制工具
- if 語句
- for 語句
- range() 函數
- break 和 continue 語句,以及循環中的 else 子句
- pass 語句
- 定義函數
- 函數定義的更多形式
- 小插曲:編碼風格
- 數據結構
- 列表的更多特性
- del 語句
- 元組和序列
- 集合
- 字典
- 循環的技巧
- 深入條件控制
- 序列和其它類型的比較
- 模塊
- 有關模塊的更多信息
- 標準模塊
- dir() 函數
- 包
- 輸入輸出
- 更漂亮的輸出格式
- 讀寫文件
- 錯誤和異常
- 語法錯誤
- 異常
- 處理異常
- 拋出異常
- 用戶自定義異常
- 定義清理操作
- 預定義的清理操作
- 類
- 名稱和對象
- Python 作用域和命名空間
- 初探類
- 補充說明
- 繼承
- 私有變量
- 雜項說明
- 迭代器
- 生成器
- 生成器表達式
- 標準庫簡介
- 操作系統接口
- 文件通配符
- 命令行參數
- 錯誤輸出重定向和程序終止
- 字符串模式匹配
- 數學
- 互聯網訪問
- 日期和時間
- 數據壓縮
- 性能測量
- 質量控制
- 自帶電池
- 標準庫簡介 —— 第二部分
- 格式化輸出
- 模板
- 使用二進制數據記錄格式
- 多線程
- 日志
- 弱引用
- 用于操作列表的工具
- 十進制浮點運算
- 虛擬環境和包
- 概述
- 創建虛擬環境
- 使用pip管理包
- 接下來?
- 交互式編輯和編輯歷史
- Tab 補全和編輯歷史
- 默認交互式解釋器的替代品
- 浮點算術:爭議和限制
- 表示性錯誤
- 附錄
- 交互模式
- 安裝和使用 Python
- 命令行與環境
- 命令行
- 環境變量
- 在Unix平臺中使用Python
- 獲取最新版本的Python
- 構建Python
- 與Python相關的路徑和文件
- 雜項
- 編輯器和集成開發環境
- 在Windows上使用 Python
- 完整安裝程序
- Microsoft Store包
- nuget.org 安裝包
- 可嵌入的包
- 替代捆綁包
- 配置Python
- 適用于Windows的Python啟動器
- 查找模塊
- 附加模塊
- 在Windows上編譯Python
- 其他平臺
- 在蘋果系統上使用 Python
- 獲取和安裝 MacPython
- IDE
- 安裝額外的 Python 包
- Mac 上的圖形界面編程
- 在 Mac 上分發 Python 應用程序
- 其他資源
- Python 語言參考
- 概述
- 其他實現
- 標注
- 詞法分析
- 行結構
- 其他形符
- 標識符和關鍵字
- 字面值
- 運算符
- 分隔符
- 數據模型
- 對象、值與類型
- 標準類型層級結構
- 特殊方法名稱
- 協程
- 執行模型
- 程序的結構
- 命名與綁定
- 異常
- 導入系統
- importlib
- 包
- 搜索
- 加載
- 基于路徑的查找器
- 替換標準導入系統
- Package Relative Imports
- 有關 main 的特殊事項
- 開放問題項
- 參考文獻
- 表達式
- 算術轉換
- 原子
- 原型
- await 表達式
- 冪運算符
- 一元算術和位運算
- 二元算術運算符
- 移位運算
- 二元位運算
- 比較運算
- 布爾運算
- 條件表達式
- lambda 表達式
- 表達式列表
- 求值順序
- 運算符優先級
- 簡單語句
- 表達式語句
- 賦值語句
- assert 語句
- pass 語句
- del 語句
- return 語句
- yield 語句
- raise 語句
- break 語句
- continue 語句
- import 語句
- global 語句
- nonlocal 語句
- 復合語句
- if 語句
- while 語句
- for 語句
- try 語句
- with 語句
- 函數定義
- 類定義
- 協程
- 最高層級組件
- 完整的 Python 程序
- 文件輸入
- 交互式輸入
- 表達式輸入
- 完整的語法規范
- Python 標準庫
- 概述
- 可用性注釋
- 內置函數
- 內置常量
- 由 site 模塊添加的常量
- 內置類型
- 邏輯值檢測
- 布爾運算 — and, or, not
- 比較
- 數字類型 — int, float, complex
- 迭代器類型
- 序列類型 — list, tuple, range
- 文本序列類型 — str
- 二進制序列類型 — bytes, bytearray, memoryview
- 集合類型 — set, frozenset
- 映射類型 — dict
- 上下文管理器類型
- 其他內置類型
- 特殊屬性
- 內置異常
- 基類
- 具體異常
- 警告
- 異常層次結構
- 文本處理服務
- string — 常見的字符串操作
- re — 正則表達式操作
- 模塊 difflib 是一個計算差異的助手
- textwrap — Text wrapping and filling
- unicodedata — Unicode 數據庫
- stringprep — Internet String Preparation
- readline — GNU readline interface
- rlcompleter — GNU readline的完成函數
- 二進制數據服務
- struct — Interpret bytes as packed binary data
- codecs — Codec registry and base classes
- 數據類型
- datetime — 基礎日期/時間數據類型
- calendar — General calendar-related functions
- collections — 容器數據類型
- collections.abc — 容器的抽象基類
- heapq — 堆隊列算法
- bisect — Array bisection algorithm
- array — Efficient arrays of numeric values
- weakref — 弱引用
- types — Dynamic type creation and names for built-in types
- copy — 淺層 (shallow) 和深層 (deep) 復制操作
- pprint — 數據美化輸出
- reprlib — Alternate repr() implementation
- enum — Support for enumerations
- 數字和數學模塊
- numbers — 數字的抽象基類
- math — 數學函數
- cmath — Mathematical functions for complex numbers
- decimal — 十進制定點和浮點運算
- fractions — 分數
- random — 生成偽隨機數
- statistics — Mathematical statistics functions
- 函數式編程模塊
- itertools — 為高效循環而創建迭代器的函數
- functools — 高階函數和可調用對象上的操作
- operator — 標準運算符替代函數
- 文件和目錄訪問
- pathlib — 面向對象的文件系統路徑
- os.path — 常見路徑操作
- fileinput — Iterate over lines from multiple input streams
- stat — Interpreting stat() results
- filecmp — File and Directory Comparisons
- tempfile — Generate temporary files and directories
- glob — Unix style pathname pattern expansion
- fnmatch — Unix filename pattern matching
- linecache — Random access to text lines
- shutil — High-level file operations
- macpath — Mac OS 9 路徑操作函數
- 數據持久化
- pickle —— Python 對象序列化
- copyreg — Register pickle support functions
- shelve — Python object persistence
- marshal — Internal Python object serialization
- dbm — Interfaces to Unix “databases”
- sqlite3 — SQLite 數據庫 DB-API 2.0 接口模塊
- 數據壓縮和存檔
- zlib — 與 gzip 兼容的壓縮
- gzip — 對 gzip 格式的支持
- bz2 — 對 bzip2 壓縮算法的支持
- lzma — 用 LZMA 算法壓縮
- zipfile — 在 ZIP 歸檔中工作
- tarfile — Read and write tar archive files
- 文件格式
- csv — CSV 文件讀寫
- configparser — Configuration file parser
- netrc — netrc file processing
- xdrlib — Encode and decode XDR data
- plistlib — Generate and parse Mac OS X .plist files
- 加密服務
- hashlib — 安全哈希與消息摘要
- hmac — 基于密鑰的消息驗證
- secrets — Generate secure random numbers for managing secrets
- 通用操作系統服務
- os — 操作系統接口模塊
- io — 處理流的核心工具
- time — 時間的訪問和轉換
- argparse — 命令行選項、參數和子命令解析器
- getopt — C-style parser for command line options
- 模塊 logging — Python 的日志記錄工具
- logging.config — 日志記錄配置
- logging.handlers — Logging handlers
- getpass — 便攜式密碼輸入工具
- curses — 終端字符單元顯示的處理
- curses.textpad — Text input widget for curses programs
- curses.ascii — Utilities for ASCII characters
- curses.panel — A panel stack extension for curses
- platform — Access to underlying platform's identifying data
- errno — Standard errno system symbols
- ctypes — Python 的外部函數庫
- 并發執行
- threading — 基于線程的并行
- multiprocessing — 基于進程的并行
- concurrent 包
- concurrent.futures — 啟動并行任務
- subprocess — 子進程管理
- sched — 事件調度器
- queue — 一個同步的隊列類
- _thread — 底層多線程 API
- _dummy_thread — _thread 的替代模塊
- dummy_threading — 可直接替代 threading 模塊。
- contextvars — Context Variables
- Context Variables
- Manual Context Management
- asyncio support
- 網絡和進程間通信
- asyncio — 異步 I/O
- socket — 底層網絡接口
- ssl — TLS/SSL wrapper for socket objects
- select — Waiting for I/O completion
- selectors — 高級 I/O 復用庫
- asyncore — 異步socket處理器
- asynchat — 異步 socket 指令/響應 處理器
- signal — Set handlers for asynchronous events
- mmap — Memory-mapped file support
- 互聯網數據處理
- email — 電子郵件與 MIME 處理包
- json — JSON 編碼和解碼器
- mailcap — Mailcap file handling
- mailbox — Manipulate mailboxes in various formats
- mimetypes — Map filenames to MIME types
- base64 — Base16, Base32, Base64, Base85 數據編碼
- binhex — 對binhex4文件進行編碼和解碼
- binascii — 二進制和 ASCII 碼互轉
- quopri — Encode and decode MIME quoted-printable data
- uu — Encode and decode uuencode files
- 結構化標記處理工具
- html — 超文本標記語言支持
- html.parser — 簡單的 HTML 和 XHTML 解析器
- html.entities — HTML 一般實體的定義
- XML處理模塊
- xml.etree.ElementTree — The ElementTree XML API
- xml.dom — The Document Object Model API
- xml.dom.minidom — Minimal DOM implementation
- xml.dom.pulldom — Support for building partial DOM trees
- xml.sax — Support for SAX2 parsers
- xml.sax.handler — Base classes for SAX handlers
- xml.sax.saxutils — SAX Utilities
- xml.sax.xmlreader — Interface for XML parsers
- xml.parsers.expat — Fast XML parsing using Expat
- 互聯網協議和支持
- webbrowser — 方便的Web瀏覽器控制器
- cgi — Common Gateway Interface support
- cgitb — Traceback manager for CGI scripts
- wsgiref — WSGI Utilities and Reference Implementation
- urllib — URL 處理模塊
- urllib.request — 用于打開 URL 的可擴展庫
- urllib.response — Response classes used by urllib
- urllib.parse — Parse URLs into components
- urllib.error — Exception classes raised by urllib.request
- urllib.robotparser — Parser for robots.txt
- http — HTTP 模塊
- http.client — HTTP協議客戶端
- ftplib — FTP protocol client
- poplib — POP3 protocol client
- imaplib — IMAP4 protocol client
- nntplib — NNTP protocol client
- smtplib —SMTP協議客戶端
- smtpd — SMTP Server
- telnetlib — Telnet client
- uuid — UUID objects according to RFC 4122
- socketserver — A framework for network servers
- http.server — HTTP 服務器
- http.cookies — HTTP state management
- http.cookiejar — Cookie handling for HTTP clients
- xmlrpc — XMLRPC 服務端與客戶端模塊
- xmlrpc.client — XML-RPC client access
- xmlrpc.server — Basic XML-RPC servers
- ipaddress — IPv4/IPv6 manipulation library
- 多媒體服務
- audioop — Manipulate raw audio data
- aifc — Read and write AIFF and AIFC files
- sunau — 讀寫 Sun AU 文件
- wave — 讀寫WAV格式文件
- chunk — Read IFF chunked data
- colorsys — Conversions between color systems
- imghdr — 推測圖像類型
- sndhdr — 推測聲音文件的類型
- ossaudiodev — Access to OSS-compatible audio devices
- 國際化
- gettext — 多語種國際化服務
- locale — 國際化服務
- 程序框架
- turtle — 海龜繪圖
- cmd — 支持面向行的命令解釋器
- shlex — Simple lexical analysis
- Tk圖形用戶界面(GUI)
- tkinter — Tcl/Tk的Python接口
- tkinter.ttk — Tk themed widgets
- tkinter.tix — Extension widgets for Tk
- tkinter.scrolledtext — 滾動文字控件
- IDLE
- 其他圖形用戶界面(GUI)包
- 開發工具
- typing — 類型標注支持
- pydoc — Documentation generator and online help system
- doctest — Test interactive Python examples
- unittest — 單元測試框架
- unittest.mock — mock object library
- unittest.mock 上手指南
- 2to3 - 自動將 Python 2 代碼轉為 Python 3 代碼
- test — Regression tests package for Python
- test.support — Utilities for the Python test suite
- test.support.script_helper — Utilities for the Python execution tests
- 調試和分析
- bdb — Debugger framework
- faulthandler — Dump the Python traceback
- pdb — The Python Debugger
- The Python Profilers
- timeit — 測量小代碼片段的執行時間
- trace — Trace or track Python statement execution
- tracemalloc — Trace memory allocations
- 軟件打包和分發
- distutils — 構建和安裝 Python 模塊
- ensurepip — Bootstrapping the pip installer
- venv — 創建虛擬環境
- zipapp — Manage executable Python zip archives
- Python運行時服務
- sys — 系統相關的參數和函數
- sysconfig — Provide access to Python's configuration information
- builtins — 內建對象
- main — 頂層腳本環境
- warnings — Warning control
- dataclasses — 數據類
- contextlib — Utilities for with-statement contexts
- abc — 抽象基類
- atexit — 退出處理器
- traceback — Print or retrieve a stack traceback
- future — Future 語句定義
- gc — 垃圾回收器接口
- inspect — 檢查對象
- site — Site-specific configuration hook
- 自定義 Python 解釋器
- code — Interpreter base classes
- codeop — Compile Python code
- 導入模塊
- zipimport — Import modules from Zip archives
- pkgutil — Package extension utility
- modulefinder — 查找腳本使用的模塊
- runpy — Locating and executing Python modules
- importlib — The implementation of import
- Python 語言服務
- parser — Access Python parse trees
- ast — 抽象語法樹
- symtable — Access to the compiler's symbol tables
- symbol — 與 Python 解析樹一起使用的常量
- token — 與Python解析樹一起使用的常量
- keyword — 檢驗Python關鍵字
- tokenize — Tokenizer for Python source
- tabnanny — 模糊縮進檢測
- pyclbr — Python class browser support
- py_compile — Compile Python source files
- compileall — Byte-compile Python libraries
- dis — Python 字節碼反匯編器
- pickletools — Tools for pickle developers
- 雜項服務
- formatter — Generic output formatting
- Windows系統相關模塊
- msilib — Read and write Microsoft Installer files
- msvcrt — Useful routines from the MS VC++ runtime
- winreg — Windows 注冊表訪問
- winsound — Sound-playing interface for Windows
- Unix 專有服務
- posix — The most common POSIX system calls
- pwd — 用戶密碼數據庫
- spwd — The shadow password database
- grp — The group database
- crypt — Function to check Unix passwords
- termios — POSIX style tty control
- tty — 終端控制功能
- pty — Pseudo-terminal utilities
- fcntl — The fcntl and ioctl system calls
- pipes — Interface to shell pipelines
- resource — Resource usage information
- nis — Interface to Sun's NIS (Yellow Pages)
- Unix syslog 庫例程
- 被取代的模塊
- optparse — Parser for command line options
- imp — Access the import internals
- 未創建文檔的模塊
- 平臺特定模塊
- 擴展和嵌入 Python 解釋器
- 推薦的第三方工具
- 不使用第三方工具創建擴展
- 使用 C 或 C++ 擴展 Python
- 自定義擴展類型:教程
- 定義擴展類型:已分類主題
- 構建C/C++擴展
- 在Windows平臺編譯C和C++擴展
- 在更大的應用程序中嵌入 CPython 運行時
- Embedding Python in Another Application
- Python/C API 參考手冊
- 概述
- 代碼標準
- 包含文件
- 有用的宏
- 對象、類型和引用計數
- 異常
- 嵌入Python
- 調試構建
- 穩定的應用程序二進制接口
- The Very High Level Layer
- Reference Counting
- 異常處理
- Printing and clearing
- 拋出異常
- Issuing warnings
- Querying the error indicator
- Signal Handling
- Exception Classes
- Exception Objects
- Unicode Exception Objects
- Recursion Control
- 標準異常
- 標準警告類別
- 工具
- 操作系統實用程序
- 系統功能
- 過程控制
- 導入模塊
- Data marshalling support
- 語句解釋及變量編譯
- 字符串轉換與格式化
- 反射
- 編解碼器注冊與支持功能
- 抽象對象層
- Object Protocol
- 數字協議
- Sequence Protocol
- Mapping Protocol
- 迭代器協議
- 緩沖協議
- Old Buffer Protocol
- 具體的對象層
- 基本對象
- 數值對象
- 序列對象
- 容器對象
- 函數對象
- 其他對象
- Initialization, Finalization, and Threads
- 在Python初始化之前
- 全局配置變量
- Initializing and finalizing the interpreter
- Process-wide parameters
- Thread State and the Global Interpreter Lock
- Sub-interpreter support
- Asynchronous Notifications
- Profiling and Tracing
- Advanced Debugger Support
- Thread Local Storage Support
- 內存管理
- 概述
- 原始內存接口
- Memory Interface
- 對象分配器
- 默認內存分配器
- Customize Memory Allocators
- The pymalloc allocator
- tracemalloc C API
- 示例
- 對象實現支持
- 在堆中分配對象
- Common Object Structures
- Type 對象
- Number Object Structures
- Mapping Object Structures
- Sequence Object Structures
- Buffer Object Structures
- Async Object Structures
- 使對象類型支持循環垃圾回收
- API 和 ABI 版本管理
- 分發 Python 模塊
- 關鍵術語
- 開源許可與協作
- 安裝工具
- 閱讀指南
- 我該如何...?
- ...為我的項目選擇一個名字?
- ...創建和分發二進制擴展?
- 安裝 Python 模塊
- 關鍵術語
- 基本使用
- 我應如何 ...?
- ... 在 Python 3.4 之前的 Python 版本中安裝 pip ?
- ... 只為當前用戶安裝軟件包?
- ... 安裝科學計算類 Python 軟件包?
- ... 使用并行安裝的多個 Python 版本?
- 常見的安裝問題
- 在 Linux 的系統 Python 版本上安裝
- 未安裝 pip
- 安裝二進制編譯擴展
- Python 常用指引
- 將 Python 2 代碼遷移到 Python 3
- 簡要說明
- 詳情
- 將擴展模塊移植到 Python 3
- 條件編譯
- 對象API的更改
- 模塊初始化和狀態
- CObject 替換為 Capsule
- 其他選項
- Curses Programming with Python
- What is curses?
- Starting and ending a curses application
- Windows and Pads
- Displaying Text
- User Input
- For More Information
- 實現描述器
- 摘要
- 定義和簡介
- 描述器協議
- 發起調用描述符
- 描述符示例
- Properties
- 函數和方法
- Static Methods and Class Methods
- 函數式編程指引
- 概述
- 迭代器
- 生成器表達式和列表推導式
- 生成器
- 內置函數
- itertools 模塊
- The functools module
- Small functions and the lambda expression
- Revision History and Acknowledgements
- 引用文獻
- 日志 HOWTO
- 日志基礎教程
- 進階日志教程
- 日志級別
- 有用的處理程序
- 記錄日志中引發的異常
- 使用任意對象作為消息
- 優化
- 日志操作手冊
- 在多個模塊中使用日志
- 在多線程中使用日志
- 使用多個日志處理器和多種格式化
- 在多個地方記錄日志
- 日志服務器配置示例
- 處理日志處理器的阻塞
- Sending and receiving logging events across a network
- Adding contextual information to your logging output
- Logging to a single file from multiple processes
- Using file rotation
- Use of alternative formatting styles
- Customizing LogRecord
- Subclassing QueueHandler - a ZeroMQ example
- Subclassing QueueListener - a ZeroMQ example
- An example dictionary-based configuration
- Using a rotator and namer to customize log rotation processing
- A more elaborate multiprocessing example
- Inserting a BOM into messages sent to a SysLogHandler
- Implementing structured logging
- Customizing handlers with dictConfig()
- Using particular formatting styles throughout your application
- Configuring filters with dictConfig()
- Customized exception formatting
- Speaking logging messages
- Buffering logging messages and outputting them conditionally
- Formatting times using UTC (GMT) via configuration
- Using a context manager for selective logging
- 正則表達式HOWTO
- 概述
- 簡單模式
- 使用正則表達式
- 更多模式能力
- 修改字符串
- 常見問題
- 反饋
- 套接字編程指南
- 套接字
- 創建套接字
- 使用一個套接字
- 斷開連接
- 非阻塞的套接字
- 排序指南
- 基本排序
- 關鍵函數
- Operator 模塊函數
- 升序和降序
- 排序穩定性和排序復雜度
- 使用裝飾-排序-去裝飾的舊方法
- 使用 cmp 參數的舊方法
- 其它
- Unicode 指南
- Unicode 概述
- Python's Unicode Support
- Reading and Writing Unicode Data
- Acknowledgements
- 如何使用urllib包獲取網絡資源
- 概述
- Fetching URLs
- 處理異常
- info and geturl
- Openers and Handlers
- Basic Authentication
- Proxies
- Sockets and Layers
- 腳注
- Argparse 教程
- 概念
- 基礎
- 位置參數介紹
- Introducing Optional arguments
- Combining Positional and Optional arguments
- Getting a little more advanced
- Conclusion
- ipaddress模塊介紹
- 創建 Address/Network/Interface 對象
- 審查 Address/Network/Interface 對象
- Network 作為 Address 列表
- 比較
- 將IP地址與其他模塊一起使用
- 實例創建失敗時獲取更多詳細信息
- Argument Clinic How-To
- The Goals Of Argument Clinic
- Basic Concepts And Usage
- Converting Your First Function
- Advanced Topics
- 使用 DTrace 和 SystemTap 檢測CPython
- Enabling the static markers
- Static DTrace probes
- Static SystemTap markers
- Available static markers
- SystemTap Tapsets
- 示例
- Python 常見問題
- Python常見問題
- 一般信息
- 現實世界中的 Python
- 編程常見問題
- 一般問題
- 核心語言
- 數字和字符串
- 性能
- 序列(元組/列表)
- 對象
- 模塊
- 設計和歷史常見問題
- 為什么Python使用縮進來分組語句?
- 為什么簡單的算術運算得到奇怪的結果?
- 為什么浮點計算不準確?
- 為什么Python字符串是不可變的?
- 為什么必須在方法定義和調用中顯式使用“self”?
- 為什么不能在表達式中賦值?
- 為什么Python對某些功能(例如list.index())使用方法來實現,而其他功能(例如len(List))使用函數實現?
- 為什么 join()是一個字符串方法而不是列表或元組方法?
- 異常有多快?
- 為什么Python中沒有switch或case語句?
- 難道不能在解釋器中模擬線程,而非得依賴特定于操作系統的線程實現嗎?
- 為什么lambda表達式不能包含語句?
- 可以將Python編譯為機器代碼,C或其他語言嗎?
- Python如何管理內存?
- 為什么CPython不使用更傳統的垃圾回收方案?
- CPython退出時為什么不釋放所有內存?
- 為什么有單獨的元組和列表數據類型?
- 列表是如何在CPython中實現的?
- 字典是如何在CPython中實現的?
- 為什么字典key必須是不可變的?
- 為什么 list.sort() 沒有返回排序列表?
- 如何在Python中指定和實施接口規范?
- 為什么沒有goto?
- 為什么原始字符串(r-strings)不能以反斜杠結尾?
- 為什么Python沒有屬性賦值的“with”語句?
- 為什么 if/while/def/class語句需要冒號?
- 為什么Python在列表和元組的末尾允許使用逗號?
- 代碼庫和插件 FAQ
- 通用的代碼庫問題
- 通用任務
- 線程相關
- 輸入輸出
- 網絡 / Internet 編程
- 數據庫
- 數學和數字
- 擴展/嵌入常見問題
- 可以使用C語言中創建自己的函數嗎?
- 可以使用C++語言中創建自己的函數嗎?
- C很難寫,有沒有其他選擇?
- 如何從C執行任意Python語句?
- 如何從C中評估任意Python表達式?
- 如何從Python對象中提取C的值?
- 如何使用Py_BuildValue()創建任意長度的元組?
- 如何從C調用對象的方法?
- 如何捕獲PyErr_Print()(或打印到stdout / stderr的任何內容)的輸出?
- 如何從C訪問用Python編寫的模塊?
- 如何從Python接口到C ++對象?
- 我使用Setup文件添加了一個模塊,為什么make失敗了?
- 如何調試擴展?
- 我想在Linux系統上編譯一個Python模塊,但是缺少一些文件。為什么?
- 如何區分“輸入不完整”和“輸入無效”?
- 如何找到未定義的g++符號__builtin_new或__pure_virtual?
- 能否創建一個對象類,其中部分方法在C中實現,而其他方法在Python中實現(例如通過繼承)?
- Python在Windows上的常見問題
- 我怎樣在Windows下運行一個Python程序?
- 我怎么讓 Python 腳本可執行?
- 為什么有時候 Python 程序會啟動緩慢?
- 我怎樣使用Python腳本制作可執行文件?
- *.pyd 文件和DLL文件相同嗎?
- 我怎樣將Python嵌入一個Windows程序?
- 如何讓編輯器不要在我的 Python 源代碼中插入 tab ?
- 如何在不阻塞的情況下檢查按鍵?
- 圖形用戶界面(GUI)常見問題
- 圖形界面常見問題
- Python 是否有平臺無關的圖形界面工具包?
- 有哪些Python的GUI工具是某個平臺專用的?
- 有關Tkinter的問題
- “為什么我的電腦上安裝了 Python ?”
- 什么是Python?
- 為什么我的電腦上安裝了 Python ?
- 我能刪除 Python 嗎?
- 術語對照表
- 文檔說明
- Python 文檔貢獻者
- 解決 Bug
- 文檔錯誤
- 使用 Python 的錯誤追蹤系統
- 開始為 Python 貢獻您的知識
- 版權
- 歷史和許可證
- 軟件歷史
- 訪問Python或以其他方式使用Python的條款和條件
- Python 3.7.3 的 PSF 許可協議
- Python 2.0 的 BeOpen.com 許可協議
- Python 1.6.1 的 CNRI 許可協議
- Python 0.9.0 至 1.2 的 CWI 許可協議
- 集成軟件的許可和認可
- Mersenne Twister
- 套接字
- Asynchronous socket services
- Cookie management
- Execution tracing
- UUencode and UUdecode functions
- XML Remote Procedure Calls
- test_epoll
- Select kqueue
- SipHash24
- strtod and dtoa
- OpenSSL
- expat
- libffi
- zlib
- cfuhash
- libmpdec