Initial attempt

```
21 tests altered the execution environment (env changed):
    test_logging test_pathlib test_profile test_pty test_pulldom
    test_pwd test_pyclbr test_pyexpat test_pyrepl test_pystats
    test_resource test_rlcompleter test_robotparser test_sax
    test_sched test_secrets test_select test_set test_shlex test_str
    test_thread

5 tests failed:
    test_capi test_cmd_line_script test_importlib test_repl
    test_sysconfig
```

Author: brettcannon

Doc/c-api/extension-modules.rst

@@ -134,9 +134,8 @@ The process of creating an extension module follows several phases:
 - By default, Python itself then creates the module object -- that is, it does
   the equivalent of calling :py:meth:`~object.__new__` when creating an object.
   This step can be overridden using the :c:data:`Py_mod_create` slot.
-- Python sets initial module attributes like :attr:`~module.__package__` and
-  :attr:`~module.__loader__`, and inserts the module object into
-  :py:attr:`sys.modules`.
+- Python sets initial module attributes like :attr:`~module.__loader__`, and
+  inserts the module object into :py:attr:`sys.modules`.
 - Afterwards, the module object is initialized in an extension-specific way
   -- the equivalent of :py:meth:`~object.__init__` when creating an object,
   or of executing top-level code in a Python-language module.
@@ -150,6 +149,9 @@ where an initialization function returns a fully constructed module.
 
    Added support for multi-phase initialization (:pep:`489`).
 
+.. deprecated-removed:: 3.12 3.15
+   :attr:`~module.__package__`
+
 
 Multiple module instances
 .........................

Doc/c-api/module.rst

@@ -33,14 +33,13 @@ Module Objects
       single: __name__ (module attribute)
       single: __doc__ (module attribute)
       single: __file__ (module attribute)
-      single: __package__ (module attribute)
       single: __loader__ (module attribute)
 
    Return a new module object with :attr:`module.__name__` set to *name*.
    The module's :attr:`!__name__`, :attr:`~module.__doc__`,
-   :attr:`~module.__package__` and :attr:`~module.__loader__` attributes are
-   filled in (all but :attr:`!__name__` are set to ``None``). The caller is
-   responsible for setting a :attr:`~module.__file__` attribute.
+   and :attr:`~module.__loader__` attributes are filled in (all but
+   :attr:`!__name__` are set to ``None``). The caller is responsible for
+   setting a :attr:`~module.__file__` attribute.
 
    Return ``NULL`` with an exception set on error.
 
@@ -50,6 +49,9 @@ Module Objects
       :attr:`~module.__package__` and :attr:`~module.__loader__` are now set to
       ``None``.
 
+   .. deprecated-removed:: 3.12 3.15
+      :attr:`~module.__package__`
+
 
 .. c:function:: PyObject* PyModule_New(const char *name)
 

Doc/library/importlib.rst

@@ -367,7 +367,6 @@ ABC hierarchy::
         - :attr:`module.__file__`
         - :attr:`module.__cached__` *(deprecated)*
         - :attr:`module.__path__`
-        - :attr:`module.__package__` *(deprecated)*
         - :attr:`module.__loader__` *(deprecated)*
 
         When :meth:`exec_module` is available then backwards-compatible
@@ -385,6 +384,9 @@ ABC hierarchy::
            other responsibilities of :meth:`load_module` when
            :meth:`exec_module` is implemented.
 
+        .. deprecated-removed:: 3.12 3.15
+           :attr:`~module.__package__` is no longer set.
+
 
 .. class:: ResourceLoader
 
@@ -1271,7 +1273,6 @@ find and load modules.
 
       (Read-only) The fully qualified name of the package the module is in (or the
       empty string for a top-level module).
-      See :attr:`module.__package__`.
       If the module is a package then this is the same as :attr:`name`.
 
    .. attribute:: has_location

Doc/library/runpy.rst

@@ -50,7 +50,7 @@ The :mod:`runpy` module provides two functions:
    overridden by :func:`run_module`.
 
    The special global variables ``__name__``, ``__spec__``, ``__file__``,
-   ``__cached__``, ``__loader__`` and ``__package__`` are set in the globals
+   ``__cached__``, and ``__loader__`` are set in the globals
    dictionary before the module code is executed. (Note that this is a
    minimal set of variables - other variables may be set implicitly as an
    interpreter implementation detail.)
@@ -63,7 +63,7 @@ The :mod:`runpy` module provides two functions:
    module (that is, ``__spec__.name`` will always be *mod_name* or
    ``mod_name + '.__main__'``, never *run_name*).
 
-   ``__file__``, ``__cached__``, ``__loader__`` and ``__package__`` are
+   ``__file__``, ``__cached__``, and ``__loader__`` are
    :ref:`set as normal <import-mod-attrs>` based on the module spec.
 
    If the argument *alter_sys* is supplied and evaluates to :const:`True`,
@@ -98,6 +98,9 @@ The :mod:`runpy` module provides two functions:
       ``__package__`` are deprecated. See
       :class:`~importlib.machinery.ModuleSpec` for alternatives.
 
+   .. deprecated-removed:: 3.12 3.15
+      ``__package__``
+
 .. function:: run_path(path_name, init_globals=None, run_name=None)
 
    .. index::
@@ -125,23 +128,23 @@ The :mod:`runpy` module provides two functions:
    overridden by :func:`run_path`.
 
    The special global variables ``__name__``, ``__spec__``, ``__file__``,
-   ``__cached__``, ``__loader__`` and ``__package__`` are set in the globals
-   dictionary before the module code is executed. (Note that this is a
-   minimal set of variables - other variables may be set implicitly as an
-   interpreter implementation detail.)
+   ``__cached__``, and ``__loader__`` are set in the globals dictionary before
+   the module code is executed. (Note that this is a minimal set of variables -
+   other variables may be set implicitly as an interpreter implementation
+   detail.)
 
    ``__name__`` is set to *run_name* if this optional argument is not
    :const:`None` and to ``'<run_path>'`` otherwise.
 
    If *file_path* directly references a script file (whether as source
    or as precompiled byte code), then ``__file__`` will be set to
-   *file_path*, and ``__spec__``, ``__cached__``, ``__loader__`` and
-   ``__package__`` will all be set to :const:`None`.
+   *file_path*, and ``__spec__``, ``__cached__``, and ``__loader__`` will all
+   be set to :const:`None`.
 
    If *file_path* is a reference to a valid :data:`sys.path` entry, then
    ``__spec__`` will be set appropriately for the imported :mod:`__main__`
    module (that is, ``__spec__.name`` will always be ``__main__``).
-   ``__file__``, ``__cached__``, ``__loader__`` and ``__package__`` will be
+   ``__file__``, ``__cached__``, and ``__loader__`` will be
    :ref:`set as normal <import-mod-attrs>` based on the module spec.
 
    A number of alterations are also made to the :mod:`sys` module. Firstly,

Doc/reference/datamodel.rst

@@ -891,7 +891,6 @@ Attribute assignment updates the module's namespace dictionary, e.g.,
 .. index::
    single: __name__ (module attribute)
    single: __spec__ (module attribute)
-   single: __package__ (module attribute)
    single: __loader__ (module attribute)
    single: __path__ (module attribute)
    single: __file__ (module attribute)
@@ -958,51 +957,6 @@ this approach.
 
    .. versionadded:: 3.4
 
-.. attribute:: module.__package__
-
-   The :term:`package` a module belongs to.
-
-   If the module is top-level (that is, not a part of any specific package)
-   then the attribute should be set to ``''`` (the empty string). Otherwise,
-   it should be set to the name of the module's package (which can be equal to
-   :attr:`module.__name__` if the module itself is a package). See :pep:`366`
-   for further details.
-
-   This attribute is used instead of :attr:`~module.__name__` to calculate
-   explicit relative imports for main modules. It defaults to ``None`` for
-   modules created dynamically using the :class:`types.ModuleType` constructor;
-   use :func:`importlib.util.module_from_spec` instead to ensure the attribute
-   is set to a :class:`str`.
-
-   It is **strongly** recommended that you use
-   :attr:`module.__spec__.parent <importlib.machinery.ModuleSpec.parent>`
-   instead of :attr:`!module.__package__`. :attr:`__package__` is now only used
-   as a fallback if :attr:`!__spec__.parent` is not set, and this fallback
-   path is deprecated.
-
-   .. versionchanged:: 3.4
-      This attribute now defaults to ``None`` for modules created dynamically
-      using the :class:`types.ModuleType` constructor.
-      Previously the attribute was optional.
-
-   .. versionchanged:: 3.6
-      The value of :attr:`!__package__` is expected to be the same as
-      :attr:`__spec__.parent <importlib.machinery.ModuleSpec.parent>`.
-      :attr:`__package__` is now only used as a fallback during import
-      resolution if :attr:`!__spec__.parent` is not defined.
-
-   .. versionchanged:: 3.10
-      :exc:`ImportWarning` is raised if an import resolution falls back to
-      :attr:`!__package__` instead of
-      :attr:`__spec__.parent <importlib.machinery.ModuleSpec.parent>`.
-
-   .. versionchanged:: 3.12
-      Raise :exc:`DeprecationWarning` instead of :exc:`ImportWarning` when
-      falling back to :attr:`!__package__` during import resolution.
-
-   .. deprecated-removed:: 3.13 3.15
-      :attr:`!__package__` will cease to be set or taken into consideration
-      by the import system or standard library.
 
 .. attribute:: module.__loader__
 
@@ -1081,6 +1035,9 @@ this approach.
       :attr:`!__cached__` will cease to be set or taken into consideration by
       the import system or standard library.
 
+.. deprecated-removed:: 3.12 3.15
+   :attr:`~module.__package__`
+
 Other writable attributes on module objects
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 

Doc/reference/import.rst

@@ -948,12 +948,8 @@ subsequent extension in :pep:`420`.
 Python 3.3.  :pep:`420` also introduced the :meth:`!find_loader` protocol as an
 alternative to :meth:`!find_module`.
 
-:pep:`366` describes the addition of the ``__package__`` attribute for
-explicit relative imports in main modules.
-
 :pep:`328` introduced absolute and explicit relative imports and initially
-proposed ``__name__`` for semantics :pep:`366` would eventually specify for
-``__package__``.
+proposed ``__name__`` for semantics.
 
 :pep:`338` defines executing modules as scripts.
 

Include/internal/pycore_global_objects_fini_generated.h

@@ -183,7 +183,6 @@ struct _Py_global_strings {
         STRUCT_FOR_ID(__or__)
         STRUCT_FOR_ID(__orig_class__)
         STRUCT_FOR_ID(__origin__)
-        STRUCT_FOR_ID(__package__)
         STRUCT_FOR_ID(__parameters__)
         STRUCT_FOR_ID(__path__)
         STRUCT_FOR_ID(__pos__)