seanpm2001
diff --git a/‎_images/hashlib-blake2-tree.png
10.8 KB b/‎_images/hashlib-blake2-tree.png
10.8 KB
diff --git a/‎_images/logging_flow.png
21.4 KB b/‎_images/logging_flow.png
21.4 KB
diff --git a/‎_images/pathlib-inheritance.png
6.28 KB b/‎_images/pathlib-inheritance.png
6.28 KB
diff --git a/‎_images/tk_msg.png
14.6 KB b/‎_images/tk_msg.png
14.6 KB
diff --git a/‎_images/turtle-star.png
33 KB b/‎_images/turtle-star.png
33 KB
diff --git a/‎_images/win_installer.png
82.4 KB b/‎_images/win_installer.png
82.4 KB
diff --git a/‎_sources/copyright.rst.txt
+1-1 b/‎_sources/copyright.rst.txt
+1-1
diff --git a/‎_sources/howto/logging-cookbook.rst.txt
+1-1 b/‎_sources/howto/logging-cookbook.rst.txt
+1-1
diff --git a/‎_sources/library/asyncio-eventloop.rst.txt
+7-7 b/‎_sources/library/asyncio-eventloop.rst.txt
+7-7
diff --git a/‎_sources/library/asyncio-policy.rst.txt
+5-4 b/‎_sources/library/asyncio-policy.rst.txt
+5-4
diff --git a/‎_sources/library/ctypes.rst.txt
+1-1 b/‎_sources/library/ctypes.rst.txt
+1-1
diff --git a/‎_sources/library/dataclasses.rst.txt
+2-2 b/‎_sources/library/dataclasses.rst.txt
+2-2
diff --git a/‎_sources/library/itertools.rst.txt
+4-4 b/‎_sources/library/itertools.rst.txt
+4-4
diff --git a/‎_sources/library/os.path.rst.txt
+12-11 b/‎_sources/library/os.path.rst.txt
+12-11
diff --git a/‎_sources/library/os.rst.txt
+2 b/‎_sources/library/os.rst.txt
+2
diff --git a/‎_sources/library/typing.rst.txt
-4 b/‎_sources/library/typing.rst.txt
-4
diff --git a/‎_sources/library/unittest.rst.txt
+2-2 b/‎_sources/library/unittest.rst.txt
+2-2
diff --git a/‎_sources/license.rst.txt
+1-1 b/‎_sources/license.rst.txt
+1-1
diff --git a/‎_sources/whatsnew/3.10.rst.txt
-13 b/‎_sources/whatsnew/3.10.rst.txt
-13
diff --git a/‎about.html
+2-2 b/‎about.html
+2-2
diff --git a/‎bugs.html
+3-3 b/‎bugs.html
+3-3
diff --git a/‎c-api/abstract.html
+2-2 b/‎c-api/abstract.html
+2-2
diff --git a/‎c-api/allocation.html
+2-2 b/‎c-api/allocation.html
+2-2
diff --git a/‎c-api/apiabiversion.html
+2-2 b/‎c-api/apiabiversion.html
+2-2
diff --git a/‎c-api/arg.html
+2-2 b/‎c-api/arg.html
+2-2
diff --git a/‎c-api/bool.html
+2-2 b/‎c-api/bool.html
+2-2
diff --git a/‎c-api/buffer.html
+2-2 b/‎c-api/buffer.html
+2-2
diff --git a/‎c-api/bytearray.html
+2-2 b/‎c-api/bytearray.html
+2-2
diff --git a/‎c-api/bytes.html
+2-2 b/‎c-api/bytes.html
+2-2
diff --git a/‎c-api/call.html
+2-2 b/‎c-api/call.html
+2-2
diff --git a/‎c-api/capsule.html
+2-2 b/‎c-api/capsule.html
+2-2
@@ -4,7 +4,7 @@ Copyright
 
 Python and this documentation is:
 
-Copyright © 2001-2022 Python Software Foundation. All rights reserved.
+Copyright © 2001-2023 Python Software Foundation. All rights reserved.
 
 Copyright © 2000 BeOpen.com. All rights reserved.
 
 
@@ -1131,7 +1131,7 @@ each request is handled by a thread:
                                                  'context can be used to '
                                                  'populate logs')
         aa = ap.add_argument
-        aa('--count', '-c', default=100, help='How many requests to simulate')
+        aa('--count', '-c', type=int, default=100, help='How many requests to simulate')
         options = ap.parse_args()
 
         # Create the dummy webapps and put them in a list which we can use to select
 
@@ -48,7 +48,7 @@ an event loop:
    running event loop.
 
    If there is no running event loop set, the function will return
-   the result of ``get_event_loop_policy().get_event_loop()`` call.
+   the result of the ``get_event_loop_policy().get_event_loop()`` call.
 
    Because this function has rather complex behavior (especially
    when custom event loop policies are in use), using the
@@ -59,15 +59,15 @@ an event loop:
    instead of using these lower level functions to manually create and close an
    event loop.
 
-   .. deprecated:: 3.10
-      Deprecation warning is emitted if there is no current event loop.
-      In Python 3.12 it will be an error.
-
    .. note::
       In Python versions 3.10.0--3.10.8 and 3.11.0 this function
-      (and other functions which used it implicitly) emitted a
+      (and other functions which use it implicitly) emitted a
       :exc:`DeprecationWarning` if there was no running event loop, even if
-      the current loop was set.
+      the current loop was set on the policy.
+      In Python versions 3.10.9, 3.11.1 and 3.12 they emit a
+      :exc:`DeprecationWarning` if there is no running event loop and no
+      current loop is set.
+      In some future Python release this will become an error.
 
 .. function:: set_event_loop(loop)
 
 
@@ -112,10 +112,11 @@ asyncio ships with the following built-in policies:
 
       On Windows, :class:`ProactorEventLoop` is now used by default.
 
-   .. deprecated:: 3.11.1
-      :meth:`get_event_loop` now emits a :exc:`DeprecationWarning` if there
-      is no current event loop set and a new event loop has been implicitly
-      created. In Python 3.12 it will be an error.
+   .. note::
+      In Python versions 3.10.9, 3.11.1 and 3.12 this function emits a
+      :exc:`DeprecationWarning` if there is no running event loop and no
+      current loop is set.
+      In some future Python release this will become an error.
 
 
 .. class:: WindowsSelectorEventLoopPolicy
 
@@ -389,7 +389,7 @@ regular, non-variadic, function arguments:
 
    libc.printf.argtypes = [ctypes.c_char_p]
 
-Because specifying the attribute does inhibit portability it is adviced to always
+Because specifying the attribute does inhibit portability it is advised to always
 specify ``argtypes`` for all variadic functions.
 
 
 
@@ -552,7 +552,7 @@ parameters to :meth:`__post_init__`.  Also see the warning about how
 Class variables
 ---------------
 
-One of two places where :func:`dataclass` actually inspects the type
+One of the few places where :func:`dataclass` actually inspects the type
 of a field is to determine if a field is a class variable as defined
 in :pep:`526`.  It does this by checking if the type of the field is
 ``typing.ClassVar``.  If a field is a ``ClassVar``, it is excluded
@@ -563,7 +563,7 @@ module-level :func:`fields` function.
 Init-only variables
 -------------------
 
-The other place where :func:`dataclass` inspects a type annotation is to
+Another place where :func:`dataclass` inspects a type annotation is to
 determine if a field is an init-only variable.  It does this by seeing
 if the type of a field is of type ``dataclasses.InitVar``.  If a field
 is an ``InitVar``, it is considered a pseudo-field called an init-only
 
@@ -33,7 +33,7 @@ by combining :func:`map` and :func:`count` to form ``map(f, count())``.
 These tools and their built-in counterparts also work well with the high-speed
 functions in the :mod:`operator` module.  For example, the multiplication
 operator can be mapped across two vectors to form an efficient dot-product:
-``sum(map(operator.mul, vector1, vector2))``.
+``sum(starmap(operator.mul, zip(vec1, vec2, strict=True)))``.
 
 
 **Infinite iterators:**
@@ -799,7 +799,7 @@ which incur interpreter overhead.
        "Returns the sequence elements n times"
        return chain.from_iterable(repeat(tuple(iterable), n))
 
-   def dotproduct(vec1, vec2):
+   def sumprod(vec1, vec2):
        "Compute a sum of products."
        return sum(starmap(operator.mul, zip(vec1, vec2, strict=True)))
 
@@ -813,7 +813,7 @@ which incur interpreter overhead.
        window = collections.deque([0], maxlen=n) * n
        for x in chain(signal, repeat(0, n-1)):
            window.append(x)
-           yield dotproduct(kernel, window)
+           yield sumprod(kernel, window)
 
    def polynomial_from_roots(roots):
        """Compute a polynomial's coefficients from its roots.
@@ -1181,7 +1181,7 @@ which incur interpreter overhead.
     >>> list(ncycles('abc', 3))
     ['a', 'b', 'c', 'a', 'b', 'c', 'a', 'b', 'c']
 
-    >>> dotproduct([1,2,3], [4,5,6])
+    >>> sumprod([1,2,3], [4,5,6])
     32
 
     >>> data = [20, 40, 24, 32, 20, 28, 16]
 
@@ -297,17 +297,18 @@ the :mod:`glob` module.)
 
 .. function:: join(path, *paths)
 
-   Join one or more path components intelligently.  The return value is the
-   concatenation of *path* and any members of *\*paths* with exactly one
-   directory separator following each non-empty part except the last, meaning
-   that the result will only end in a separator if the last part is empty.  If
-   a component is an absolute path, all previous components are thrown away
-   and joining continues from the absolute path component.
-
-   On Windows, the drive letter is not reset when an absolute path component
-   (e.g., ``r'\foo'``) is encountered.  If a component contains a drive
-   letter, all previous components are thrown away and the drive letter is
-   reset.  Note that since there is a current directory for each drive,
+   Join one or more path segments intelligently.  The return value is the
+   concatenation of *path* and all members of *\*paths*, with exactly one
+   directory separator following each non-empty part except the last. That is,
+   if the last part is empty, the result will end in a separator. If
+   a segment is an absolute path (which on Windows requires both a drive and a
+   root), then all previous segments are ignored and joining continues from the
+   absolute path segment.
+
+   On Windows, the drive is not reset when a rooted path segment (e.g.,
+   ``r'\foo'``) is encountered. If a segment is on a different drive or is an
+   absolute path, all previous segments are ignored and the drive is reset. Note
+   that since there is a current directory for each drive,
    ``os.path.join("c:", "foo")`` represents a path relative to the current
    directory on drive :file:`C:` (:file:`c:foo`), not :file:`c:\\foo`.
 
 
@@ -2372,6 +2372,8 @@ features:
    will fail with an :exc:`OSError` subclass in a number of cases:
 
    On Windows, if *dst* exists a :exc:`FileExistsError` is always raised.
+   The operation may fail if *src* and *dst* are on different filesystems. Use
+   :func:`shutil.move` to support moves to a different filesystem.
 
    On Unix, if *src* is a file and *dst* is a directory or vice-versa, an
    :exc:`IsADirectoryError` or a :exc:`NotADirectoryError` will be raised
 
@@ -2767,10 +2767,6 @@ Introspection helpers
    .. versionchanged:: 3.9
       Added ``include_extras`` parameter as part of :pep:`593`.
 
-   .. versionchanged:: 3.10
-      Calling ``get_type_hints()`` on a class no longer returns the annotations
-      of its base classes.
-
    .. versionchanged:: 3.11
       Previously, ``Optional[t]`` was added for function and method annotations
       if a default value equal to ``None`` was set.
 
@@ -1983,12 +1983,12 @@ Loading and running tests
    .. attribute:: testNamePatterns
 
       List of Unix shell-style wildcard test name patterns that test methods
-      have to match to be included in test suites (see ``-v`` option).
+      have to match to be included in test suites (see ``-k`` option).
 
       If this attribute is not ``None`` (the default), all test methods to be
       included in test suites must match one of the patterns in this list.
       Note that matches are always performed using :meth:`fnmatch.fnmatchcase`,
-      so unlike patterns passed to the ``-v`` option, simple substring patterns
+      so unlike patterns passed to the ``-k`` option, simple substring patterns
       will have to be converted using ``*`` wildcards.
 
       This affects all the :meth:`loadTestsFrom\*` methods.
 
@@ -100,7 +100,7 @@ PSF LICENSE AGREEMENT FOR PYTHON |release|
       analyze, test, perform and/or display publicly, prepare derivative works,
       distribute, and otherwise use Python |release| alone or in any derivative
       version, provided, however, that PSF's License Agreement and PSF's notice of
-      copyright, i.e., "Copyright © 2001-2022 Python Software Foundation; All Rights
+      copyright, i.e., "Copyright © 2001-2023 Python Software Foundation; All Rights
       Reserved" are retained in Python |release| alone or in any derivative version
       prepared by Licensee.
 
 
@@ -1708,19 +1708,6 @@ Deprecated
   scheduled for removal in Python 3.12.
   (Contributed by Erlend E. Aasland in :issue:`42264`.)
 
-* :func:`asyncio.get_event_loop` now emits a deprecation warning if there is
-  no running event loop. In the future it will be an alias of
-  :func:`~asyncio.get_running_loop`.
-  :mod:`asyncio` functions which implicitly create :class:`~asyncio.Future`
-  or :class:`~asyncio.Task` objects now emit
-  a deprecation warning if there is no running event loop and no explicit
-  *loop* argument is passed: :func:`~asyncio.ensure_future`,
-  :func:`~asyncio.wrap_future`, :func:`~asyncio.gather`,
-  :func:`~asyncio.shield`, :func:`~asyncio.as_completed` and constructors of
-  :class:`~asyncio.Future`, :class:`~asyncio.Task`,
-  :class:`~asyncio.StreamReader`, :class:`~asyncio.StreamReaderProtocol`.
-  (Contributed by Serhiy Storchaka in :issue:`39529`.)
-
 * The undocumented built-in function ``sqlite3.enable_shared_cache`` is now
   deprecated, scheduled for removal in Python 3.12.  Its use is strongly
   discouraged by the SQLite3 documentation.  See `the SQLite3 docs
 
@@ -281,11 +281,11 @@ <h3>瀏覽</h3>
 <br />
     <br />
 
-    最後更新於 1月 06, 2023。
+    最後更新於 1月 11, 2023。
     <a href="/bugs.html">Found a bug</a>?
     <br />
 
-    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.1 建立。
+    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.3 建立。
     </div>
 
   </body>
 
@@ -203,7 +203,7 @@ <h2>說明文件的錯誤<a class="headerlink" href="#documentation-bugs" title=
 </section>
 <section id="getting-started-contributing-to-python-yourself">
 <span id="contributing-to-python"></span><h2>開始讓自己貢獻 Python<a class="headerlink" href="#getting-started-contributing-to-python-yourself" title="本標頭的永久連結">¶</a></h2>
-<p>除了只是回報您所發現的錯誤之外，同樣也歡迎您提交修正它們的修補程式 (patch)。您可以在 <a class="reference external" href="https://mail.python.org/mailman3/lists/core-mentorship.python.org/">Python 開發者指南</a>中找到如何開始修補 Python 的更多資訊。如果您有任何問題，<a class="reference external" href="https://devguide.python.org/">核心導師郵寄清單</a>是一個友善的地方，您可以在那裡得到，關於 Python 修正錯誤的過程中，所有問題的答案。</p>
+<p>除了只是回報您所發現的錯誤之外，同樣也歡迎您提交修正它們的修補程式 (patch)。您可以在 <a class="reference external" href="https://devguide.python.org/">Python 開發者指南</a>中找到如何開始修補 Python 的更多資訊。如果您有任何問題，<a class="reference external" href="https://mail.python.org/mailman3/lists/core-mentorship.python.org/">核心導師郵寄清單</a>是一個友善的地方，您可以在那裡得到，關於 Python 修正錯誤的過程中，所有問題的答案。</p>
 </section>
 </section>
 
@@ -316,11 +316,11 @@ <h3>瀏覽</h3>
 <br />
     <br />
 
-    最後更新於 1月 06, 2023。
+    最後更新於 1月 11, 2023。
     <a href="/bugs.html">Found a bug</a>?
     <br />
 
-    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.1 建立。
+    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.3 建立。
     </div>
 
   </body>
 
@@ -291,11 +291,11 @@ <h3>瀏覽</h3>
 <br />
     <br />
 
-    最後更新於 1月 06, 2023。
+    最後更新於 1月 11, 2023。
     <a href="/bugs.html">Found a bug</a>?
     <br />
 
-    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.1 建立。
+    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.3 建立。
     </div>
 
   </body>
 
@@ -305,11 +305,11 @@ <h3>瀏覽</h3>
 <br />
     <br />
 
-    最後更新於 1月 06, 2023。
+    最後更新於 1月 11, 2023。
     <a href="/bugs.html">Found a bug</a>?
     <br />
 
-    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.1 建立。
+    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.3 建立。
     </div>
 
   </body>
 
@@ -339,11 +339,11 @@ <h3>瀏覽</h3>
 <br />
     <br />
 
-    最後更新於 1月 06, 2023。
+    最後更新於 1月 11, 2023。
     <a href="/bugs.html">Found a bug</a>?
     <br />
 
-    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.1 建立。
+    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.3 建立。
     </div>
 
   </body>
 
@@ -877,11 +877,11 @@ <h3>瀏覽</h3>
 <br />
     <br />
 
-    最後更新於 1月 06, 2023。
+    最後更新於 1月 11, 2023。
     <a href="/bugs.html">Found a bug</a>?
     <br />
 
-    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.1 建立。
+    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.3 建立。
     </div>
 
   </body>
 
@@ -289,11 +289,11 @@ <h3>瀏覽</h3>
 <br />
     <br />
 
-    最後更新於 1月 06, 2023。
+    最後更新於 1月 11, 2023。
     <a href="/bugs.html">Found a bug</a>?
     <br />
 
-    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.1 建立。
+    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.3 建立。
     </div>
 
   </body>
 
@@ -964,11 +964,11 @@ <h3>瀏覽</h3>
 <br />
     <br />
 
-    最後更新於 1月 06, 2023。
+    最後更新於 1月 11, 2023。
     <a href="/bugs.html">Found a bug</a>?
     <br />
 
-    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.1 建立。
+    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.3 建立。
     </div>
 
   </body>
 
@@ -365,11 +365,11 @@ <h3>瀏覽</h3>
 <br />
     <br />
 
-    最後更新於 1月 06, 2023。
+    最後更新於 1月 11, 2023。
     <a href="/bugs.html">Found a bug</a>?
     <br />
 
-    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.1 建立。
+    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.3 建立。
     </div>
 
   </body>
 
@@ -481,11 +481,11 @@ <h3>瀏覽</h3>
 <br />
     <br />
 
-    最後更新於 1月 06, 2023。
+    最後更新於 1月 11, 2023。
     <a href="/bugs.html">Found a bug</a>?
     <br />
 
-    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.1 建立。
+    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.3 建立。
     </div>
 
   </body>
 
@@ -606,11 +606,11 @@ <h3>瀏覽</h3>
 <br />
     <br />
 
-    最後更新於 1月 06, 2023。
+    最後更新於 1月 11, 2023。
     <a href="/bugs.html">Found a bug</a>?
     <br />
 
-    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.1 建立。
+    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.3 建立。
     </div>
 
   </body>
 
@@ -402,11 +402,11 @@ <h3>瀏覽</h3>
 <br />
     <br />
 
-    最後更新於 1月 06, 2023。
+    最後更新於 1月 11, 2023。
     <a href="/bugs.html">Found a bug</a>?
     <br />
 
-    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.1 建立。
+    使用 <a href="https://www.sphinx-doc.org/">Sphinx</a> 6.1.3 建立。
     </div>
 
   </body>