pyc -> .pyc files

Author: benjaminp

Doc/library/compileall.rst

@@ -86,11 +86,12 @@ compile Python sources.
 .. cmdoption:: --invalidation-mode [timestamp|checked-hash|unchecked-hash]
 
    Control how the generated pycs will be invalidated at runtime. The default
-   setting, ``timestamp``, means that pyc files with the source timestamp and
-   size embedded will be generated. The ``checked-hash`` and ``unchecked-hash``
-   values cause hash-based pycs to be generated. Hash-based pycs embed a hash of
-   the source file contents rather than a timestamp. See :ref:`pyc-invalidation`
-   for more information on how Python validates bytecode cache files at runtime.
+   setting, ``timestamp``, means that ``.pyc`` files with the source timestamp
+   and size embedded will be generated. The ``checked-hash`` and
+   ``unchecked-hash`` values cause hash-based pycs to be generated. Hash-based
+   pycs embed a hash of the source file contents rather than a timestamp. See
+   :ref:`pyc-invalidation` for more information on how Python validates bytecode
+   cache files at runtime.
 
 .. versionchanged:: 3.2
    Added the ``-i``, ``-b`` and ``-h`` options.

Doc/library/importlib.rst

@@ -1332,8 +1332,8 @@ an :term:`importer`.
 
 .. function:: source_hash(source_bytes)
 
-   Return the hash of *source_bytes* as byte string. A hash-based pyc embeds the
-   :func:`source_hash` of the corresponding source file's contents in its
+   Return the hash of *source_bytes* as bytes. A hash-based ``.pyc`` file embeds
+   the :func:`source_hash` of the corresponding source file's contents in its
    header.
 
    .. versionadded:: 3.7

Doc/library/py_compile.rst

@@ -54,7 +54,8 @@ byte-code cache files in the directory containing the source code.
    level of the current interpreter.
 
    *invalidation_mode* should be a member of the :class:`PycInvalidationMode`
-   enum and controls how the generated pycs are invalidated at runtime.
+   enum and controls how the generated ``.pyc`` files are invalidated at
+   runtime.
 
    .. versionchanged:: 3.2
       Changed default value of *cfile* to be :PEP:`3147`-compliant.  Previous
@@ -75,32 +76,33 @@ byte-code cache files in the directory containing the source code.
 .. class:: PycInvalidationMode
 
    A enumeration of possible methods the interpreter can use to determine
-   whether a bytecode file is up to date with a source file. The pyc indicates
-   the desired invalidation mode in its header. See :ref:`pyc-invalidation` for
-   more information on how Python invalidates pycs at runtime.
+   whether a bytecode file is up to date with a source file. The ``.pyc`` file
+   indicates the desired invalidation mode in its header. See
+   :ref:`pyc-invalidation` for more information on how Python invalidates
+   ``.pyc`` files at runtime.
 
    .. versionadded:: 3.7
 
    .. attribute:: TIMESTAMP
 
-      The pyc includes the timestamp and size of the source file, which Python
-      will compare against the metadata of the source file at runtime to
-      determine if the pyc needs to be regenerated.
+      The ``.pyc`` file includes the timestamp and size of the source file,
+      which Python will compare against the metadata of the source file at
+      runtime to determine if the ``.pyc`` file needs to be regenerated.
 
    .. attribute:: CHECKED_HASH
 
-      The pyc includes a hash of the source file content, which Python will
-      compare against the source at runtime to determine if the pyc needs to be
-      regenerated.
+      The ``.pyc`` file includes a hash of the source file content, which Python
+      will compare against the source at runtime to determine if the ``.pyc``
+      file needs to be regenerated.
 
    .. attribute:: UNCHECKED_HASH
 
-      Like :attr:`CHECKED_HASH`, the pyc includes a hash of the source file
-      content. However, Python will at runtime assume the pyc is up to date and
-      not validate the pyc against the source file at all.
+      Like :attr:`CHECKED_HASH`, the ``.pyc`` file includes a hash of the source
+      file content. However, Python will at runtime assume the ``.pyc`` file is
+      up to date and not validate the ``.pyc`` against the source file at all.
 
-      This option is useful when the pycs are kept up to date by some system
-      external to Python like a build system.
+      This option is useful when the ``.pycs`` are kept up to date by some
+      system external to Python like a build system.
 
 
 .. function:: main(args=None)

Doc/reference/import.rst

@@ -689,17 +689,18 @@ metadata.
 
 Python also supports "hash-based" cache files, which store a hash of a source
 file contents rather than its metadata. There are two variants of hash-based
-pycs: checked and unchecked. For checked hash-based pycs, Python validates the
-cache file by hashing the source file and comparing the resulting hash with the
-hash in the cache file. If a checked hash-based cache file is found to be
-invalid, Python regenerates it and writes a new checked hash-based cache
-file. For unchecked hash-based pycs, Python simply assumes the cache file is
-valid if it exists. Hash-based pyc validation behavior may be override with the
-:option:`--check-hash-based-pycs` flag.
+``.pyc`` files: checked and unchecked. For checked hash-based ``.pyc`` files,
+Python validates the cache file by hashing the source file and comparing the
+resulting hash with the hash in the cache file. If a checked hash-based cache
+file is found to be invalid, Python regenerates it and writes a new checked
+hash-based cache file. For unchecked hash-based ``.pyc`` files, Python simply
+assumes the cache file is valid if it exists. Hash-based ``.pyc`` files
+validation behavior may be override with the :option:`--check-hash-based-pycs`
+flag.
 
 .. versionchanged:: 3.7
-   Added hash-based pycs. Previously, Python only supported timestamp-based pyc
-   invalidation.
+   Added hash-based ``.pyc`` files. Previously, Python only supported
+   timestamp-based invalidation of bytecode caches.
 
 
 The Path Based Finder

Doc/using/cmdline.rst

@@ -212,15 +212,16 @@ Miscellaneous options
 
 .. cmdoption:: --check-hash-based-pycs default|always|never
 
-   Control the validation behavior of hash-based pycs. See
+   Control the validation behavior of hash-based ``.pyc`` files. See
    :ref:`pyc-invalidation`. When set to ``default``, checked and unchecked
    hash-based bytecode cache files are validated according to their default
-   semantics. When set to ``always``, all hash-based pycs, whether checked or
-   unchecked, are validated against their corresponding source file. When set to
-   ``never``, hash-based pycs are not validated against their corresponding
-   source files.
+   semantics. When set to ``always``, all hash-based ``.pyc`` files, whether
+   checked or unchecked, are validated against their corresponding source
+   file. When set to ``never``, hash-based ``.pyc`` files are not validated
+   against their corresponding source files.
 
-   The semantics of timestamp-based pycs are unaffected by this option.
+   The semantics of timestamp-based ``.pyc`` files are unaffected by this
+   option.
 
 
 .. cmdoption:: -d

Doc/whatsnew/3.7.rst

@@ -201,25 +201,26 @@ Hash-based pycs
 ---------------
 
 Python has traditionally checked the up-to-dateness of bytecode cache files
-(i.e., pycs) by comparing the source metadata (last-modified timestamp and size)
-with source metadata saved in the cache file header when it was generated. While
-effective, this invalidation method has its drawbacks. When filesystem
-timestamps are too coarse, Python can miss source updates, leading to user
-confusion. Additionally, having a timestamp in the cache file is problematic for
-`build reproduciblity <https://reproducible-builds.org/>`_ and content-based
-build systems.
+(i.e., ``.pyc`` files) by comparing the source metadata (last-modified timestamp
+and size) with source metadata saved in the cache file header when it was
+generated. While effective, this invalidation method has its drawbacks. When
+filesystem timestamps are too coarse, Python can miss source updates, leading to
+user confusion. Additionally, having a timestamp in the cache file is
+problematic for `build reproduciblity <https://reproducible-builds.org/>`_ and
+content-based build systems.
 
 :pep:`552` extends the pyc format to allow the hash of the source file to be
-used for invalidation instead of the source timestamp. Such pycs are called
-"hash-based". By default, Python still uses timestamp-based invalidation and
-does not generate hash-based pycs at runtime. Hash-based pycs may be generated
-with :mod:`py_compile` or :mod:`compileall`.
-
-Hash-based pycs come in two variants: checked and unchecked. Python validates
-checked hash-based pycs against the source file at runtime but doesn't do so for
-unchecked hash-based pycs. Unchecked hash-based pycs are a useful performance
-optimization for environments where a system external to Python (e.g., the build
-system) is responsible for keeping pycs up-to-date.
+used for invalidation instead of the source timestamp. Such ``.pyc`` files are
+called "hash-based". By default, Python still uses timestamp-based invalidation
+and does not generate hash-based ``.pyc`` files at runtime. Hash-based ``.pyc``
+files may be generated with :mod:`py_compile` or :mod:`compileall`.
+
+Hash-based ``.pyc`` files come in two variants: checked and unchecked. Python
+validates checked hash-based ``.pyc`` files against the corresponding source
+files at runtime but doesn't do so for unchecked hash-based pycs. Unchecked
+hash-based ``.pyc`` files are a useful performance optimization for environments
+where a system external to Python (e.g., the build system) is responsible for
+keeping ``.pyc`` files up-to-date.
 
 See :ref:`pyc-invalidation` for more information.