IMAPClient 3.1.0__tar.gz → 4.0.1__tar.gz

{imapclient-3.1.0 → imapclient-4.0.1}/AUTHORS.rst

@@ -47,3 +47,5 @@ project:
 - @axoroll7
 - Sean Whalen
 - Peter Wienemann 
+- Arnout Engelen
+

imapclient-4.0.1/IMAPClient.egg-info/PKG-INFO

@@ -0,0 +1,195 @@
+Metadata-Version: 2.4
+Name: IMAPClient
+Version: 4.0.1
+Summary: Easy-to-use, Pythonic and complete IMAP client library
+Author-email: Menno Finlay-Smits <hello@menno.io>
+Maintainer-email: IMAPClient Maintainers <imapclient@groups.io>
+Project-URL: Homepage, https://github.com/mjs/imapclient/
+Keywords: imap,client,email,mail
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Natural Language :: English
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Communications :: Email :: Post-Office :: IMAP
+Classifier: Topic :: Internet
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: System :: Networking
+Requires-Python: >=3.8.0
+Description-Content-Type: text/x-rst
+License-File: COPYING
+License-File: AUTHORS.rst
+Dynamic: license-file
+
+Essentials
+----------
+IMAPClient is an easy-to-use, Pythonic and complete IMAP client
+library.
+
+=========================  ========================================
+Supported Python versions  3.8 - 3.14
+License                    New BSD
+Project home               https://github.com/mjs/imapclient/
+PyPI                       https://pypi.python.org/pypi/IMAPClient
+Documentation              https://imapclient.readthedocs.io/
+Discussions                https://github.com/mjs/imapclient/discussions
+Test Status                |build master|
+=========================  ========================================
+
+.. |build master| image:: https://github.com/mjs/imapclient/actions/workflows/main.yml/badge.svg
+   :target: https://github.com/mjs/imapclient/actions
+   :alt: master branch
+
+Features
+--------
+- Arguments and return values are natural Python types.
+- IMAP server responses are fully parsed and readily usable.
+- IMAP unique message IDs (UIDs) are handled transparently. There is
+  no need to call different methods to use UIDs.
+- Escaping for internationalised mailbox names is transparently
+  handled.  Unicode mailbox names may be passed as input wherever a
+  folder name is accepted.
+- Time zones are transparently handled including when the server and
+  client are in different zones.
+- Convenience methods are provided for commonly used functionality.
+- Exceptions are raised when errors occur.
+
+Example
+-------
+
+.. code-block:: python
+
+    from imapclient import IMAPClient
+
+    # context manager ensures the session is cleaned up
+    with IMAPClient(host="imap.host.org") as client:
+        client.login('someone', 'secret')
+        client.select_folder('INBOX')
+
+        # search criteria are passed in a straightforward way
+        # (nesting is supported)
+        messages = client.search(['NOT', 'DELETED'])
+
+        # fetch selectors are passed as a simple list of strings.
+        response = client.fetch(messages, ['FLAGS', 'RFC822.SIZE'])
+
+        # `response` is keyed by message id and contains parsed,
+        # converted response items.
+        for message_id, data in response.items():
+            print('{id}: {size} bytes, flags={flags}'.format(
+                id=message_id,
+                size=data[b'RFC822.SIZE'],
+                flags=data[b'FLAGS']))
+
+Why IMAPClient?
+---------------
+You may ask: "why create another IMAP client library for Python?
+Doesn't the Python standard library already have imaplib?".
+
+The problem with imaplib is that it's very low-level. It expects
+string values where lists or tuples would be more appropriate and
+returns server responses almost unparsed. As IMAP server responses can
+be quite complex this means everyone using imaplib ends up writing
+their own fragile parsing routines.
+
+Also, imaplib doesn't make good use of exceptions. This means you need
+to check the return value of each call to imaplib to see if what you
+just did was successful.
+
+IMAPClient actually uses imaplib internally. This may change at some
+point in the future.
+
+Installing IMAPClient
+---------------------
+IMAPClient is listed on PyPI and can be installed with `uv
+<https://docs.astral.sh/uv/>`_::
+
+    uv add imapclient
+
+More installation methods are described in the documentation.
+
+Documentation
+-------------
+IMAPClient's manual is available at http://imapclient.readthedocs.io/.
+Release notes can be found at
+http://imapclient.readthedocs.io/#release-history.
+
+See the `examples` directory in the root of project source for
+examples of how to use IMAPClient.
+
+Current Status
+--------------
+You should feel confident using IMAPClient for production purposes. 
+
+In order to clearly communicate version compatibility, IMAPClient
+will strictly adhere to the `Semantic Versioning <http://semver.org>`_
+scheme from version 1.0 onwards.
+
+The project's home page is https://github.com/mjs/imapclient/ (this
+currently redirects to the IMAPClient Github site). Details about
+upcoming versions and planned features/fixes can be found in the issue
+tracker on Github. The maintainers also blog about IMAPClient
+news. Those articles can be found `here
+<http://menno.io/tags/imapclient>`_.
+
+Discussions
+-----------
+`Github Discussions`_ can be used to ask questions, propose changes or praise
+the project maintainers :)
+
+.. _`Github Discussions`: https://github.com/mjs/imapclient/discussions
+
+Working on IMAPClient
+---------------------
+The `contributing documentation
+<http://imapclient.rtfd.io/en/master/contributing.html>`_ contains
+information for those interested in improving IMAPClient.
+
+IMAP Servers
+------------
+IMAPClient is heavily tested against Dovecot, Gmail, Fastmail.fm
+(who use a modified Cyrus implementation), Office365 and Yahoo. Access
+to accounts on other IMAP servers/services for testing would be
+greatly appreciated.
+
+Interactive Console
+-------------------
+This script connects an IMAPClient instance using the command line
+args given and starts an interactive session. This is useful for
+exploring the IMAPClient API and testing things out, avoiding the
+steps required to set up an IMAPClient instance.
+
+The IPython shell is used if it is installed. Otherwise the
+code.interact() function from the standard library is used.
+
+The interactive console functionality can be accessed by running the
+``imapclient-interact`` script that is installed alongside IMAPClient,
+or by invoking the interact module like this::
+
+    uv run python -m imapclient.interact ...
+
+"Live" Tests
+------------
+IMAPClient includes a series of live, functional tests which exercise
+it against a live IMAP account. These are useful for ensuring
+compatibility with a given IMAP server implementation.
+
+The livetest functionality is run using the ``imapclient-livetest``
+script that is installed alongside IMAPClient::
+
+    uv run imapclient-livetest <livetest.ini> [ optional unittest arguments ]
+
+The configuration file format is
+`described in the main documentation <http://imapclient.rtfd.io/#configuration-file-format>`_.
+
+**WARNING**: The operations used by livetest are destructive and could
+cause unintended loss of data. That said, as of version 0.9, livetest
+limits its activity to a folder it creates and subfolders of that
+folder. It *should* be safe to use with any IMAP account but please
+don't run livetest against a truly important IMAP account.
+
+Please include the output of imapclient-livetest with an issue if it
+fails to run successfully against a particular IMAP server. Reports of
+successful runs are also welcome.  Please include the type and version
+of the IMAP server, if known.

imapclient-4.0.1/IMAPClient.egg-info/SOURCES.txt

@@ -0,0 +1,43 @@
+AUTHORS.rst
+COPYING
+README.rst
+pyproject.toml
+IMAPClient.egg-info/PKG-INFO
+IMAPClient.egg-info/SOURCES.txt
+IMAPClient.egg-info/dependency_links.txt
+IMAPClient.egg-info/entry_points.txt
+IMAPClient.egg-info/top_level.txt
+imapclient/__init__.py
+imapclient/config.py
+imapclient/datetime_util.py
+imapclient/exceptions.py
+imapclient/fixed_offset.py
+imapclient/imap4.py
+imapclient/imap_utf7.py
+imapclient/imapclient.py
+imapclient/interact.py
+imapclient/livetest.py
+imapclient/response_lexer.py
+imapclient/response_parser.py
+imapclient/response_types.py
+imapclient/testable_imapclient.py
+imapclient/tls.py
+imapclient/typing_imapclient.py
+imapclient/util.py
+imapclient/version.py
+tests/test_auth.py
+tests/test_datetime_util.py
+tests/test_enable.py
+tests/test_fixed_offset.py
+tests/test_folder_status.py
+tests/test_imap_utf7.py
+tests/test_imapclient.py
+tests/test_init.py
+tests/test_response_lexer.py
+tests/test_response_parser.py
+tests/test_search.py
+tests/test_sort.py
+tests/test_starttls.py
+tests/test_store.py
+tests/test_thread.py
+tests/test_util_functions.py

imapclient-4.0.1/IMAPClient.egg-info/entry_points.txt

@@ -0,0 +1,3 @@
+[console_scripts]
+imapclient-interact = imapclient.interact:main
+imapclient-livetest = imapclient.livetest:main

imapclient-4.0.1/PKG-INFO

@@ -0,0 +1,195 @@
+Metadata-Version: 2.4
+Name: IMAPClient
+Version: 4.0.1
+Summary: Easy-to-use, Pythonic and complete IMAP client library
+Author-email: Menno Finlay-Smits <hello@menno.io>
+Maintainer-email: IMAPClient Maintainers <imapclient@groups.io>
+Project-URL: Homepage, https://github.com/mjs/imapclient/
+Keywords: imap,client,email,mail
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: OS Independent
+Classifier: Natural Language :: English
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Communications :: Email :: Post-Office :: IMAP
+Classifier: Topic :: Internet
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: System :: Networking
+Requires-Python: >=3.8.0
+Description-Content-Type: text/x-rst
+License-File: COPYING
+License-File: AUTHORS.rst
+Dynamic: license-file
+
+Essentials
+----------
+IMAPClient is an easy-to-use, Pythonic and complete IMAP client
+library.
+
+=========================  ========================================
+Supported Python versions  3.8 - 3.14
+License                    New BSD
+Project home               https://github.com/mjs/imapclient/
+PyPI                       https://pypi.python.org/pypi/IMAPClient
+Documentation              https://imapclient.readthedocs.io/
+Discussions                https://github.com/mjs/imapclient/discussions
+Test Status                |build master|
+=========================  ========================================
+
+.. |build master| image:: https://github.com/mjs/imapclient/actions/workflows/main.yml/badge.svg
+   :target: https://github.com/mjs/imapclient/actions
+   :alt: master branch
+
+Features
+--------
+- Arguments and return values are natural Python types.
+- IMAP server responses are fully parsed and readily usable.
+- IMAP unique message IDs (UIDs) are handled transparently. There is
+  no need to call different methods to use UIDs.
+- Escaping for internationalised mailbox names is transparently
+  handled.  Unicode mailbox names may be passed as input wherever a
+  folder name is accepted.
+- Time zones are transparently handled including when the server and
+  client are in different zones.
+- Convenience methods are provided for commonly used functionality.
+- Exceptions are raised when errors occur.
+
+Example
+-------
+
+.. code-block:: python
+
+    from imapclient import IMAPClient
+
+    # context manager ensures the session is cleaned up
+    with IMAPClient(host="imap.host.org") as client:
+        client.login('someone', 'secret')
+        client.select_folder('INBOX')
+
+        # search criteria are passed in a straightforward way
+        # (nesting is supported)
+        messages = client.search(['NOT', 'DELETED'])
+
+        # fetch selectors are passed as a simple list of strings.
+        response = client.fetch(messages, ['FLAGS', 'RFC822.SIZE'])
+
+        # `response` is keyed by message id and contains parsed,
+        # converted response items.
+        for message_id, data in response.items():
+            print('{id}: {size} bytes, flags={flags}'.format(
+                id=message_id,
+                size=data[b'RFC822.SIZE'],
+                flags=data[b'FLAGS']))
+
+Why IMAPClient?
+---------------
+You may ask: "why create another IMAP client library for Python?
+Doesn't the Python standard library already have imaplib?".
+
+The problem with imaplib is that it's very low-level. It expects
+string values where lists or tuples would be more appropriate and
+returns server responses almost unparsed. As IMAP server responses can
+be quite complex this means everyone using imaplib ends up writing
+their own fragile parsing routines.
+
+Also, imaplib doesn't make good use of exceptions. This means you need
+to check the return value of each call to imaplib to see if what you
+just did was successful.
+
+IMAPClient actually uses imaplib internally. This may change at some
+point in the future.
+
+Installing IMAPClient
+---------------------
+IMAPClient is listed on PyPI and can be installed with `uv
+<https://docs.astral.sh/uv/>`_::
+
+    uv add imapclient
+
+More installation methods are described in the documentation.
+
+Documentation
+-------------
+IMAPClient's manual is available at http://imapclient.readthedocs.io/.
+Release notes can be found at
+http://imapclient.readthedocs.io/#release-history.
+
+See the `examples` directory in the root of project source for
+examples of how to use IMAPClient.
+
+Current Status
+--------------
+You should feel confident using IMAPClient for production purposes. 
+
+In order to clearly communicate version compatibility, IMAPClient
+will strictly adhere to the `Semantic Versioning <http://semver.org>`_
+scheme from version 1.0 onwards.
+
+The project's home page is https://github.com/mjs/imapclient/ (this
+currently redirects to the IMAPClient Github site). Details about
+upcoming versions and planned features/fixes can be found in the issue
+tracker on Github. The maintainers also blog about IMAPClient
+news. Those articles can be found `here
+<http://menno.io/tags/imapclient>`_.
+
+Discussions
+-----------
+`Github Discussions`_ can be used to ask questions, propose changes or praise
+the project maintainers :)
+
+.. _`Github Discussions`: https://github.com/mjs/imapclient/discussions
+
+Working on IMAPClient
+---------------------
+The `contributing documentation
+<http://imapclient.rtfd.io/en/master/contributing.html>`_ contains
+information for those interested in improving IMAPClient.
+
+IMAP Servers
+------------
+IMAPClient is heavily tested against Dovecot, Gmail, Fastmail.fm
+(who use a modified Cyrus implementation), Office365 and Yahoo. Access
+to accounts on other IMAP servers/services for testing would be
+greatly appreciated.
+
+Interactive Console
+-------------------
+This script connects an IMAPClient instance using the command line
+args given and starts an interactive session. This is useful for
+exploring the IMAPClient API and testing things out, avoiding the
+steps required to set up an IMAPClient instance.
+
+The IPython shell is used if it is installed. Otherwise the
+code.interact() function from the standard library is used.
+
+The interactive console functionality can be accessed by running the
+``imapclient-interact`` script that is installed alongside IMAPClient,
+or by invoking the interact module like this::
+
+    uv run python -m imapclient.interact ...
+
+"Live" Tests
+------------
+IMAPClient includes a series of live, functional tests which exercise
+it against a live IMAP account. These are useful for ensuring
+compatibility with a given IMAP server implementation.
+
+The livetest functionality is run using the ``imapclient-livetest``
+script that is installed alongside IMAPClient::
+
+    uv run imapclient-livetest <livetest.ini> [ optional unittest arguments ]
+
+The configuration file format is
+`described in the main documentation <http://imapclient.rtfd.io/#configuration-file-format>`_.
+
+**WARNING**: The operations used by livetest are destructive and could
+cause unintended loss of data. That said, as of version 0.9, livetest
+limits its activity to a folder it creates and subfolders of that
+folder. It *should* be safe to use with any IMAP account but please
+don't run livetest against a truly important IMAP account.
+
+Please include the output of imapclient-livetest with an issue if it
+fails to run successfully against a particular IMAP server. Reports of
+successful runs are also welcome.  Please include the type and version
+of the IMAP server, if known.

{imapclient-3.1.0 → imapclient-4.0.1}/README.rst

@@ -4,7 +4,6 @@ IMAPClient is an easy-to-use, Pythonic and complete IMAP client
 library.
 
 =========================  ========================================
-Current version            3.0.1
 Supported Python versions  3.8 - 3.14
 License                    New BSD
 Project home               https://github.com/mjs/imapclient/
@@ -79,9 +78,10 @@ point in the future.
 
 Installing IMAPClient
 ---------------------
-IMAPClient is listed on PyPI and can be installed with pip::
+IMAPClient is listed on PyPI and can be installed with `uv
+<https://docs.astral.sh/uv/>`_::
 
-    pip install imapclient
+    uv add imapclient
 
 More installation methods are described in the documentation.
 
@@ -139,11 +139,11 @@ steps required to set up an IMAPClient instance.
 The IPython shell is used if it is installed. Otherwise the
 code.interact() function from the standard library is used.
 
-The interactive console functionality can be accessed running the
-interact.py script in the root of the source tree or by invoking the
-interact module like this::
+The interactive console functionality can be accessed by running the
+``imapclient-interact`` script that is installed alongside IMAPClient,
+or by invoking the interact module like this::
 
-    python -m imapclient.interact ...
+    uv run python -m imapclient.interact ...
 
 "Live" Tests
 ------------
@@ -151,10 +151,10 @@ IMAPClient includes a series of live, functional tests which exercise
 it against a live IMAP account. These are useful for ensuring
 compatibility with a given IMAP server implementation.
 
-The livetest functionality are run from the root of the project source
-like this::
+The livetest functionality is run using the ``imapclient-livetest``
+script that is installed alongside IMAPClient::
 
-    python livetest.py <livetest.ini> [ optional unittest arguments ]
+    uv run imapclient-livetest <livetest.ini> [ optional unittest arguments ]
 
 The configuration file format is
 `described in the main documentation <http://imapclient.rtfd.io/#configuration-file-format>`_.
@@ -165,7 +165,7 @@ limits its activity to a folder it creates and subfolders of that
 folder. It *should* be safe to use with any IMAP account but please
 don't run livetest against a truly important IMAP account.
 
-Please include the output of livetest.py with an issue if it fails
-to run successfully against a particular IMAP server. Reports of
+Please include the output of imapclient-livetest with an issue if it
+fails to run successfully against a particular IMAP server. Reports of
 successful runs are also welcome.  Please include the type and version
 of the IMAP server, if known.

{imapclient-3.1.0 → imapclient-4.0.1}/imapclient/__init__.py

@@ -8,6 +8,5 @@
 from .imapclient import *  # noqa: F401,F403
 from .response_parser import *  # noqa: F401,F403
 from .tls import *  # noqa: F401,F403
-from .version import author as __author__  # noqa: F401
 from .version import version as __version__  # noqa: F401
 from .version import version_info  # noqa: F401

{imapclient-3.1.0 → imapclient-4.0.1}/imapclient/config.py

@@ -40,7 +40,7 @@ def get_config_defaults() -> Dict[str, Any]:
 def parse_config_file(filename: str) -> argparse.Namespace:
     """Parse INI files containing IMAP connection details.
 
-    Used by livetest.py and interact.py
+    Used by imapclient.livetest and imapclient.interact
     """
 
     parser = configparser.ConfigParser(get_string_config_defaults())

{imapclient-3.1.0 → imapclient-4.0.1}/imapclient/imap4.py

@@ -10,16 +10,7 @@ from typing import Optional
 class IMAP4WithTimeout(imaplib.IMAP4):
     def __init__(self, address: str, port: int, timeout: Optional[float]) -> None:
         self._timeout = timeout
-        imaplib.IMAP4.__init__(self, address, port)
-
-    def open(
-        self, host: str = "", port: int = 143, timeout: Optional[float] = None
-    ) -> None:
-        # This is overridden to make it consistent across Python versions.
-        self.host = host
-        self.port = port
-        self.sock = self._create_socket(timeout)
-        self.file = self.sock.makefile("rb")
+        super().__init__(address, port, timeout=timeout)
 
     def _create_socket(self, timeout: Optional[float] = None) -> socket.socket:
         return socket.create_connection(

{imapclient-3.1.0 → imapclient-4.0.1}/imapclient/imapclient.py

@@ -22,7 +22,7 @@ from .datetime_util import datetime_to_INTERNALDATE, format_criteria_date
 from .imap_utf7 import decode as decode_utf7
 from .imap_utf7 import encode as encode_utf7
 from .response_parser import parse_fetch_response, parse_message_list, parse_response
-from .util import assert_imap_protocol, chunk, to_bytes, to_unicode
+from .util import assert_imap_protocol, chunk, to_bytes, to_ints, to_unicode
 
 if hasattr(select, "poll"):
     POLL_SUPPORT = True
@@ -830,7 +830,11 @@ class IMAPClient:
         """
         logger.debug("< UNSELECT")
         # IMAP4 class has no `unselect` method so we can't use `_command_and_check` there
-        _typ, data = self._imap._simple_command("UNSELECT")
+        typ, data = self._imap._simple_command("UNSELECT")
+        # Mirror imaplib.IMAP4.unselect: return the connection to the
+        # authenticated state so subsequent commands (e.g. ENABLE) are legal.
+        if typ == "OK":
+            self._imap.state = "AUTH"
         return data[0]
 
     def _process_select_response(self, resp):
@@ -1375,6 +1379,9 @@ class IMAPClient:
                     b'INTERNALDATE': datetime.datetime(2011, 2, 24, 19, 30, 36),
                     b'SEQ': 110}}
 
+        Note that due to IMAP unsolicited FETCH responses the return
+        value may include fields not matching the original data query.
+        It is up to the caller to handle that gracefully.
         """
         if not messages:
             return {}
@@ -1391,7 +1398,13 @@ class IMAPClient:
         typ, data = self._imap._command_complete("FETCH", tag)
         self._checkok("fetch", typ, data)
         typ, data = self._imap._untagged_response(typ, data, "FETCH")
-        return parse_fetch_response(data, self.normalise_times, self.use_uid)
+        response = parse_fetch_response(data, self.normalise_times, self.use_uid)
+        # Drop unsolicited responses for other messages
+        return {
+            message_id: response[message_id]
+            for message_id in to_ints(messages)
+            if message_id in response
+        }
 
     def append(self, folder, msg, flags=(), msg_time=None):
         """Append a message to *folder*.
@@ -1789,7 +1802,14 @@ class IMAPClient:
         )
         if silent:
             return None
-        return self._filter_fetch_dict(parse_fetch_response(data), fetch_key)
+        response = parse_fetch_response(data)
+        # Drop unsolicited responses for other messages
+        without_unsolicited = {
+            message_id: response[message_id]
+            for message_id in to_ints(messages)
+            if message_id in response
+        }
+        return self._filter_fetch_dict(without_unsolicited, fetch_key)
 
     def _filter_fetch_dict(self, fetch_dict, key):
         return dict((msgid, data[key]) for msgid, data in fetch_dict.items())

{imapclient-3.1.0 → imapclient-4.0.1/imapclient}/livetest.py

@@ -19,18 +19,18 @@ import unittest
 from datetime import datetime
 from email.utils import make_msgid
 
-from imapclient.config import create_client_from_config, parse_config_file
-from imapclient.exceptions import IMAPClientError
-from imapclient.fixed_offset import FixedOffset
-from imapclient.imapclient import (
+from .config import create_client_from_config, parse_config_file
+from .exceptions import IMAPClientError
+from .fixed_offset import FixedOffset
+from .imapclient import (
     _dict_bytes_normaliser,
     DELETED,
     IMAPClient,
     RECENT,
     SocketTimeout,
 )
-from imapclient.response_types import Address, Envelope
-from imapclient.util import to_bytes, to_unicode
+from .response_types import Address, Envelope
+from .util import to_bytes, to_unicode
 
 # TODO cleaner verbose output: avoid "__main__" and separator between classes
 
@@ -62,9 +62,7 @@ Content-Transfer-Encoding: 7bit
 Here is the second part.
 
 --===============1534046211==--
-""".replace(
-    "\n", "\r\n"
-)
+""".replace("\n", "\r\n")
 
 
 SMILE = "\u263a"
@@ -75,9 +73,7 @@ Subject: stuff
 Content-Type: text/plain; charset="UTF-8"
 
 \xe2\x98\xba
-""".replace(
-    b"\n", b"\r\n"
-)
+""".replace(b"\n", b"\r\n")
 
 
 class _TestBase(unittest.TestCase):

{imapclient-3.1.0 → imapclient-4.0.1}/imapclient/response_types.py

@@ -141,8 +141,13 @@ class BodyData(_BodyDataType):
                 if TYPE_CHECKING:
                     assert isinstance(part, tuple)
                 parts.append(part)
-            return cls(([cls.create(part) for part in parts],) + response[i:])
-        return cls(response)
+            # The runtime representation of BodyData mixes converted
+            # BodyData/list items with raw, not-yet-converted response
+            # atoms. _BodyDataType can't precisely express this shape, so
+            # the construction below can't be typed exactly.
+            body_parts = ([cls.create(part) for part in parts],) + response[i:]
+            return cls(body_parts)  # type: ignore[arg-type]
+        return cls(response)  # type: ignore[arg-type]
 
     @property
     def is_multipart(self) -> bool: