python-docx-oss 0.1.1__tar.gz → 0.2.0__tar.gz

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0}/HISTORY.md

@@ -1,5 +1,16 @@
 ## Release History
 
+**0.2.0 (2026-08-24)**
+
+- Added direct loading from raw DOCX bytes with ``Document(bytes)``.
+- Added ``Document.to_bytes()`` for in-memory export and ``Document.copy()``
+  for independent document snapshots.
+- Added safe removal of Custom XML parts, including their document and property
+  relationships.
+- Added real-document EMF round-trip coverage and corrected the EMF MIME type.
+- Documented the capability matrix, upstream maintenance policy, and
+  compatibility boundary with official ``python-docx``.
+
 **0.1.1 (2026-08-21)**
 
 - Added Python 3.14 support and CI coverage for Python 3.12 through 3.14.

{python_docx_oss-0.1.1/src/python_docx_oss.egg-info → python_docx_oss-0.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-docx-oss
-Version: 0.1.1
+Version: 0.2.0
 Summary: Create, read, and update Microsoft Word .docx files.
 Author: Ethan St Lee
 License-Expression: MIT
@@ -53,18 +53,19 @@ Use it when an application needs more than basic paragraphs and tables: custom d
 metadata, application-owned XML, vector images, floating pictures, East Asian fonts,
 or low-level package and relationship access.
 
-## Features
+## Capability Matrix
 
-| Capability | Support |
-| --- | --- |
-| Documents, paragraphs, runs, tables, styles, sections, headers, and footers | ✓ |
-| Custom document properties | ✓ |
-| Custom XML parts | ✓ |
-| SVG and EMF images | ✓ |
-| Inline and floating pictures | ✓ |
-| Independent ASCII, High ANSI, and East Asian font controls | ✓ |
-| Low-level OPC parts and relationships | ✓ |
-| File-path and in-memory stream processing | ✓ |
+| Capability | Status | Primary API |
+| --- | --- | --- |
+| Documents, paragraphs, tables, styles, sections, headers, and footers | Stable | `Document()` and document object APIs |
+| Custom document properties | Stable | `document.custom_properties` |
+| Custom XML lifecycle | Stable | `add_custom_xml_part()`, `delete_custom_xml_part()` |
+| SVG and EMF images | Stable | `add_picture()` |
+| Inline and floating pictures | Stable | `add_picture()`, `add_float_picture()` |
+| Latin and East Asian font controls | Stable | `run.font.name`, `run.font.hAnsi`, `run.font.eastAsia` |
+| Low-level OPC parts and relationships | Stable | `document.part.package`, `part.rels` |
+| In-memory read, export, and independent copies | Stable | `Document()`, `to_bytes()`, `copy()` |
+| Package inspection, diff, and sanitization | Planned | — |
 
 ## Installation
 
@@ -170,6 +171,8 @@ available through `Document.add_float_picture()` and `Run.add_float_picture()`.
 - [API reference](docs/index.rst#api-documentation)
 - [Custom properties](docs/user/custom-properties.rst)
 - [Custom XML](docs/user/custom-xml.rst)
+- [python-docx compatibility](docs/user/compatibility.rst)
+- [Upstream maintenance](docs/dev/upstream-maintenance.rst)
 - [Release history](HISTORY.md)
 
 ## Quality and Testing

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0}/README.md

@@ -24,18 +24,19 @@ Use it when an application needs more than basic paragraphs and tables: custom d
 metadata, application-owned XML, vector images, floating pictures, East Asian fonts,
 or low-level package and relationship access.
 
-## Features
-
-| Capability | Support |
-| --- | --- |
-| Documents, paragraphs, runs, tables, styles, sections, headers, and footers | ✓ |
-| Custom document properties | ✓ |
-| Custom XML parts | ✓ |
-| SVG and EMF images | ✓ |
-| Inline and floating pictures | ✓ |
-| Independent ASCII, High ANSI, and East Asian font controls | ✓ |
-| Low-level OPC parts and relationships | ✓ |
-| File-path and in-memory stream processing | ✓ |
+## Capability Matrix
+
+| Capability | Status | Primary API |
+| --- | --- | --- |
+| Documents, paragraphs, tables, styles, sections, headers, and footers | Stable | `Document()` and document object APIs |
+| Custom document properties | Stable | `document.custom_properties` |
+| Custom XML lifecycle | Stable | `add_custom_xml_part()`, `delete_custom_xml_part()` |
+| SVG and EMF images | Stable | `add_picture()` |
+| Inline and floating pictures | Stable | `add_picture()`, `add_float_picture()` |
+| Latin and East Asian font controls | Stable | `run.font.name`, `run.font.hAnsi`, `run.font.eastAsia` |
+| Low-level OPC parts and relationships | Stable | `document.part.package`, `part.rels` |
+| In-memory read, export, and independent copies | Stable | `Document()`, `to_bytes()`, `copy()` |
+| Package inspection, diff, and sanitization | Planned | — |
 
 ## Installation
 
@@ -141,6 +142,8 @@ available through `Document.add_float_picture()` and `Run.add_float_picture()`.
 - [API reference](docs/index.rst#api-documentation)
 - [Custom properties](docs/user/custom-properties.rst)
 - [Custom XML](docs/user/custom-xml.rst)
+- [python-docx compatibility](docs/user/compatibility.rst)
+- [Upstream maintenance](docs/dev/upstream-maintenance.rst)
 - [Release history](HISTORY.md)
 
 ## Quality and Testing

python_docx_oss-0.2.0/docs/dev/upstream-maintenance.rst

@@ -0,0 +1,95 @@
+Upstream maintenance
+====================
+
+``python-docx-oss`` evolves as an independent DOCX SDK. Its source, tests,
+versioning, and releases are authoritative in this repository. The official
+`python-docx repository <https://github.com/python-openxml/python-docx>`_ is an
+upstream source of compatible APIs, bug fixes, and OPC/WordprocessingML
+improvements; it is not the development repository for ``python-docx-oss``.
+
+Upstream baseline
+-----------------
+
+The current upstream baseline is ``python-docx v1.2.0`` at commit
+``e45454602b53e8e572b179ccf1c91093ec9f4ed7``.
+
+This baseline identifies the last official release whose changes have been
+evaluated as a whole. It does not imply compatibility with every private or
+internal upstream API.
+
+No local repository layout is required. A maintainer may obtain upstream source
+using a temporary clone, a read-only Git remote, a release archive, or another
+equivalent method. Maintenance instructions and project documentation must not
+depend on sibling directories, personal filesystem paths, or local-only
+branches.
+
+When to evaluate upstream
+-------------------------
+
+Evaluate upstream changes when:
+
+* ``python-docx`` publishes a release;
+* upstream fixes a security, data-loss, or document-compatibility issue;
+* a supported downstream workflow needs a new standard API; or
+* an upcoming ``python-docx-oss`` release needs a baseline refresh.
+
+Continuous synchronization with individual upstream commits is not required.
+
+Integration workflow
+--------------------
+
+#. Obtain the target upstream tag or commit and compare it with the recorded
+   baseline.
+#. Review release notes and classify changes to public APIs, OPC packaging,
+   XML handling, templates, schemas, tests, and documentation.
+#. Create a dedicated branch in ``python-docx-oss`` for the integration. The
+   branch name and the location used to obtain upstream source are not part of
+   the public maintenance contract.
+#. Integrate the relevant changes as a reviewable change set. Preserve upstream
+   history when practical, but prefer a clear, auditable result over a blind
+   merge.
+#. Resolve conflicts according to the compatibility rules below.
+#. Run the full verification gates and review the package artifacts.
+#. Update this baseline, compatibility notes, and ``HISTORY.md`` in the same
+   integration change.
+
+Compatibility and conflict rules
+--------------------------------
+
+Standard public ``python-docx`` behavior is preferred unless adopting it would
+break an API intentionally supported by ``python-docx-oss``. An upstream
+integration must preserve the supported capabilities documented in the
+Capability Matrix and covered by the regression test suite.
+
+Compatibility with upstream private APIs is not guaranteed. Intentional public
+API differences must be recorded in compatibility or divergence notes rather
+than hidden in conflict-resolution commits.
+
+Verification gates
+------------------
+
+An upstream integration is complete only when the repository CI passes. This
+includes:
+
+* unit, integration, and acceptance tests on all supported Python versions;
+* lint, formatting, and scoped type checks;
+* documentation and distribution builds; and
+* real-DOCX round trips required by the Capability Matrix and regression test
+  suite.
+
+The resulting wheel and source distribution must contain the expected package
+data and install without also installing the official ``python-docx``
+distribution, because both projects provide the ``docx`` import namespace.
+
+Recording the result
+--------------------
+
+For each completed baseline refresh, record:
+
+* the upstream tag and resolved commit;
+* the material APIs and fixes adopted;
+* intentionally omitted upstream changes and their rationale; and
+* any new compatibility boundary visible to users.
+
+Temporary comparison checkouts, remotes, and branches are local implementation
+details and are not part of the permanent project record.

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0}/docs/index.rst

@@ -97,6 +97,7 @@ User Guide
    user/shapes
    user/custom-properties
    user/custom-xml
+   user/compatibility
 
 
 API Documentation
@@ -117,11 +118,11 @@ API Documentation
    api/shared
    api/enum/index
 
-
 Contributor Guide
 -----------------
 
 .. toctree::
    :maxdepth: 1
 
+   dev/upstream-maintenance
    dev/analysis/index

python_docx_oss-0.2.0/docs/user/compatibility.rst

@@ -0,0 +1,48 @@
+python-docx compatibility
+=========================
+
+``python-docx-oss`` and the official ``python-docx`` project share the
+``docx`` import namespace and a common code lineage. They are separate Python
+distributions with independent versions and release schedules.
+
+Compatibility target
+--------------------
+
+The current upstream baseline is ``python-docx v1.2.0`` at commit
+``e45454602b53e8e572b179ccf1c91093ec9f4ed7``.
+
+Public APIs inherited from that baseline are compatibility targets unless an
+intentional difference is documented. Compatibility with private modules,
+private attributes, undocumented XML internals, or implementation details is
+not guaranteed.
+
+Extensions provided by ``python-docx-oss`` are additive where practical. The
+project's current supported and planned features are maintained in the
+Capability Matrix rather than duplicated here.
+
+Distribution boundary
+---------------------
+
+Do not install ``python-docx`` and ``python-docx-oss`` into the same Python
+environment. Both distributions provide the ``docx`` package, so installing
+both can produce an environment whose imported files depend on installation
+order.
+
+Applications should declare exactly one of the two distributions as a direct
+dependency. Migrating an existing application normally does not require import
+changes, but its use of undocumented upstream internals must be reviewed.
+
+Intentional differences
+-----------------------
+
+An intentional difference is recorded when ``python-docx-oss`` changes a
+public inherited API or its observable behavior. Each record must identify:
+
+* the affected public API;
+* the behavior of the recorded upstream baseline;
+* the ``python-docx-oss`` behavior and rationale; and
+* any migration action required by callers.
+
+Additive APIs and capabilities do not require individual divergence records;
+they belong in the API documentation and Capability Matrix. Upstream baseline
+changes follow the :doc:`../dev/upstream-maintenance` policy.

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0}/docs/user/custom-xml.rst

@@ -89,7 +89,15 @@ Delete a child by passing the element itself::
     customers.delete_item(customer)
 
 The indexes in ``items`` can change after deletion. Removing an entire Custom
-XML part is not currently provided by this API.
+XML part uses the main document part::
+
+    document.part.delete_custom_xml_part(customers)
+
+The Custom XML part, its relationship from the main document, and any related
+``itemPropsN.xml`` property part are omitted the next time the document is
+saved. The deleted ``itemN.xml`` name becomes available for later additions.
+Attempting to delete a part that is not related to the document, including a
+part that has already been deleted, raises ``ValueError``.
 
 Existing relationships to Custom XML property parts, such as
 ``itemPropsN.xml``, are preserved during load/save round trips.

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0}/docs/user/documents.rst

@@ -67,13 +67,18 @@ Opening a file-like document
 |docx| can open a document from a so-called *file-like* object. It can also
 save to a file-like object. This can be handy when you want to get the source
 or target document over a network connection or from a database and don't want
-to (or aren't allowed to) interact with the file system. A ``.docx`` package is
-binary, so an in-memory stream must be an :class:`io.BytesIO` object::
-
-    from io import BytesIO
+to (or aren't allowed to) interact with the file system. Raw DOCX bytes can be
+opened directly::
 
     from docx import Document
 
+    with open("foobar.docx", "rb") as file:
+        document = Document(file.read())
+
+A binary file-like object such as :class:`io.BytesIO` is also supported::
+
+    from io import BytesIO
+
     with open("foobar.docx", "rb") as file:
         source_stream = BytesIO(file.read())
     document = Document(source_stream)
@@ -92,5 +97,23 @@ After saving, rewind the output stream before reading it or opening it again::
 Always open ``.docx`` files in binary mode (``"rb"`` for reading and ``"wb"``
 for writing).
 
+Exporting and copying in memory
+-------------------------------
+
+Use :meth:`Document.to_bytes <docx.document.Document.to_bytes>` when the complete
+DOCX package needs to be uploaded, cached, returned over HTTP, or stored in a
+database::
+
+    content = document.to_bytes()
+
+Use :meth:`Document.copy <docx.document.Document.copy>` to create an independent
+snapshot that can be modified without changing the source document::
+
+    customer_document = document.copy()
+    customer_document.add_paragraph("Customer-specific content")
+
+The copy has its own XML trees, parts, and relationships. Both operations stay
+in memory and do not create temporary files.
+
 Okay, so you've got a document open and are pretty sure you can save it
 somewhere later. Next step is to get some content in there ...

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0}/src/docx/__init__.py

@@ -13,7 +13,7 @@ from docx.api import Document
 if TYPE_CHECKING:
     from docx.opc.part import Part
 
-__version__ = "0.1.1"
+__version__ = "0.2.0"
 
 
 __all__ = ["Document"]

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0}/src/docx/api.py

@@ -5,6 +5,7 @@ Provides a syntactically more convenient API for interacting with the OpcPackage
 
 from __future__ import annotations
 
+import io
 import os
 from typing import IO, TYPE_CHECKING, cast
 
@@ -16,18 +17,20 @@ if TYPE_CHECKING:
     from docx.parts.document import DocumentPart
 
 
-def Document(docx: str | IO[bytes] | None = None) -> DocumentObject:
+def Document(docx: str | bytes | IO[bytes] | None = None) -> DocumentObject:
     """Return a |Document| object loaded from `docx`, where `docx` can be either a path
-    to a ``.docx`` file (a string) or a file-like object.
+    to a ``.docx`` file, raw DOCX bytes, or a binary file-like object.
 
     If `docx` is missing or ``None``, the built-in default document "template" is
     loaded.
     """
     docx = _default_docx_path() if docx is None else docx
+    source_name = "<bytes>" if isinstance(docx, bytes) else docx
+    docx = io.BytesIO(docx) if isinstance(docx, bytes) else docx
     document_part = cast("DocumentPart", Package.open(docx).main_document_part)
     if document_part.content_type != CT.WML_DOCUMENT_MAIN:
         tmpl = "file '%s' is not a Word file, content type is '%s'"
-        raise ValueError(tmpl % (docx, document_part.content_type))
+        raise ValueError(tmpl % (source_name, document_part.content_type))
     return document_part.document
 
 

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0}/src/docx/document.py

@@ -5,8 +5,10 @@
 
 from __future__ import annotations
 
+import io
 from typing import IO, TYPE_CHECKING, Iterator, List, Sequence
 
+from docx.api import Document as open_document
 from docx.blkcntnr import BlockItemContainer
 from docx.enum.section import WD_SECTION
 from docx.enum.text import WD_BREAK
@@ -182,6 +184,10 @@ class Document(ElementProxy):
         """A |CoreProperties| object providing Dublin Core properties of document."""
         return self._part.core_properties
 
+    def copy(self) -> Document:
+        """Return an independent in-memory snapshot of this document."""
+        return open_document(io.BytesIO(self.to_bytes()))
+
     @property
     def custom_properties(self) -> CustomProperties:
         """A |CustomProperties| object providing custom properties of document."""
@@ -249,6 +255,12 @@ class Document(ElementProxy):
         """
         return self._body.tables
 
+    def to_bytes(self) -> bytes:
+        """Serialize this document as a complete in-memory DOCX package."""
+        with io.BytesIO() as stream:
+            self.save(stream)
+            return stream.getvalue()
+
     @property
     def _block_width(self) -> Length:
         """A |Length| object specifying the space between margins in last section."""

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0}/src/docx/image/constants.py

@@ -101,6 +101,7 @@ class MIME_TYPE:
     """Image content types."""
 
     BMP = "image/bmp"
+    EMF = "image/x-emf"
     GIF = "image/gif"
     JPEG = "image/jpeg"
     PNG = "image/png"

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0}/src/docx/image/emf.py

@@ -13,7 +13,7 @@ class Emf(BaseImageHeader):
     @property
     def content_type(self):
         """
-        MIME content type for this image, unconditionally `image/emf` for
+        MIME content type for this image, unconditionally `image/x-emf` for
         EMF images.
         """
         return MIME_TYPE.EMF
@@ -38,7 +38,6 @@ class Emf(BaseImageHeader):
         y1 = stream_rdr.read_long(20)
 
         frame = tuple(map(stream_rdr.read_long, (24, 28, 32, 36)))
-        size = x1 - x0, y1 - y0
 
         xdpi = 2540.0 * (x1 - x0) / (frame[2] - frame[0])
         ydpi = 2540.0 * (y1 - y0) / (frame[3] - frame[1])

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0}/src/docx/opc/rel.py

@@ -28,6 +28,11 @@ class Relationships(Dict[str, "_Relationship"]):
             self._target_parts_by_rId[rId] = target
         return rel
 
+    def __delitem__(self, rId: str) -> None:
+        """Remove the relationship and its cached target-part reference."""
+        super().__delitem__(rId)
+        self._target_parts_by_rId.pop(rId, None)
+
     def get_or_add(self, reltype: str, target_part: Part) -> _Relationship:
         """Return relationship of `reltype` to `target_part`, newly added if not already
         present in collection."""

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0}/src/docx/parts/customxml.py

@@ -59,7 +59,7 @@ class CustomXmlPart(XmlPart):
         """
         return self.element.getchildren()
 
-    def add_item(self, tag: str, text: str = "", **attrib):
+    def add_item(self, tag: str, text: str = "", **attrib: str) -> None:
         """
         Add a child element to root.
         """

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0}/src/docx/parts/document.py

@@ -54,6 +54,24 @@ class DocumentPart(StoryPart):
         rId = self.relate_to(header_part, RT.HEADER)
         return header_part, rId
 
+    def delete_custom_xml_part(self, part: CustomXmlPart) -> None:
+        """Delete a Custom XML part related to this document.
+
+        Related Custom XML property parts are detached with the part and omitted from
+        the package when it is next saved.
+        """
+        matching_rIds = [
+            rId
+            for rId, rel in self.rels.items()
+            if rel.reltype == RT.CUSTOM_XML and not rel.is_external and rel.target_part is part
+        ]
+        if not matching_rIds:
+            raise ValueError(f"part '{part.partname}' is not related to this document")
+
+        part.drop_rels(lambda rel: rel.reltype == RT.CUSTOM_XML_PROPS)
+        for rId in matching_rIds:
+            del self.rels[rId]
+
     @property
     def comments(self) -> Comments:
         """|Comments| object providing access to the comments added to this document."""

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0/src/python_docx_oss.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-docx-oss
-Version: 0.1.1
+Version: 0.2.0
 Summary: Create, read, and update Microsoft Word .docx files.
 Author: Ethan St Lee
 License-Expression: MIT
@@ -53,18 +53,19 @@ Use it when an application needs more than basic paragraphs and tables: custom d
 metadata, application-owned XML, vector images, floating pictures, East Asian fonts,
 or low-level package and relationship access.
 
-## Features
+## Capability Matrix
 
-| Capability | Support |
-| --- | --- |
-| Documents, paragraphs, runs, tables, styles, sections, headers, and footers | ✓ |
-| Custom document properties | ✓ |
-| Custom XML parts | ✓ |
-| SVG and EMF images | ✓ |
-| Inline and floating pictures | ✓ |
-| Independent ASCII, High ANSI, and East Asian font controls | ✓ |
-| Low-level OPC parts and relationships | ✓ |
-| File-path and in-memory stream processing | ✓ |
+| Capability | Status | Primary API |
+| --- | --- | --- |
+| Documents, paragraphs, tables, styles, sections, headers, and footers | Stable | `Document()` and document object APIs |
+| Custom document properties | Stable | `document.custom_properties` |
+| Custom XML lifecycle | Stable | `add_custom_xml_part()`, `delete_custom_xml_part()` |
+| SVG and EMF images | Stable | `add_picture()` |
+| Inline and floating pictures | Stable | `add_picture()`, `add_float_picture()` |
+| Latin and East Asian font controls | Stable | `run.font.name`, `run.font.hAnsi`, `run.font.eastAsia` |
+| Low-level OPC parts and relationships | Stable | `document.part.package`, `part.rels` |
+| In-memory read, export, and independent copies | Stable | `Document()`, `to_bytes()`, `copy()` |
+| Package inspection, diff, and sanitization | Planned | — |
 
 ## Installation
 
@@ -170,6 +171,8 @@ available through `Document.add_float_picture()` and `Run.add_float_picture()`.
 - [API reference](docs/index.rst#api-documentation)
 - [Custom properties](docs/user/custom-properties.rst)
 - [Custom XML](docs/user/custom-xml.rst)
+- [python-docx compatibility](docs/user/compatibility.rst)
+- [Upstream maintenance](docs/dev/upstream-maintenance.rst)
 - [Release history](HISTORY.md)
 
 ## Quality and Testing

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0}/src/python_docx_oss.egg-info/SOURCES.txt

@@ -53,6 +53,7 @@ docs/api/enum/WdTabLeader.rst
 docs/api/enum/WdTableDirection.rst
 docs/api/enum/WdUnderline.rst
 docs/api/enum/index.rst
+docs/dev/upstream-maintenance.rst
 docs/dev/analysis/index.rst
 docs/dev/analysis/features/comments.rst
 docs/dev/analysis/features/coreprops.rst
@@ -90,6 +91,7 @@ docs/dev/analysis/schema/ct_document.rst
 docs/dev/analysis/schema/ct_p.rst
 docs/user/api-concepts.rst
 docs/user/comments.rst
+docs/user/compatibility.rst
 docs/user/custom-properties.rst
 docs/user/custom-xml.rst
 docs/user/documents.rst

{python_docx_oss-0.1.1 → python_docx_oss-0.2.0}/tests/integration/customxml/test_custom_xml_roundtrip.py

@@ -88,3 +88,33 @@ class DescribeMultipleCustomXmlParts:
 
         with pytest.raises(ValueError, match="part already exists at '/customXml/item1.xml'"):
             document.part.add_custom_xml_part("<duplicate/>", file_name="item1")
+
+    def it_round_trips_deleting_a_part_and_reuses_its_partname(self):
+        document = Document(io.BytesIO(FIXTURE.read_bytes()))
+        customers = _parts_by_name(document)["/customXml/item1.xml"]
+
+        document.part.delete_custom_xml_part(customers)
+        replacement = document.part.add_custom_xml_part(f'<audit xmlns="{AUDIT_NS}"/>')
+        assert str(replacement.partname) == "/customXml/item1.xml"
+
+        output = io.BytesIO()
+        document.save(output)
+        reopened = Document(io.BytesIO(output.getvalue()))
+        reopened_parts = _parts_by_name(reopened)
+
+        assert set(reopened_parts) == {"/customXml/item1.xml", "/customXml/item3.xml"}
+        assert reopened_parts["/customXml/item1.xml"].tag == f"{{{AUDIT_NS}}}audit"
+        with ZipFile(io.BytesIO(output.getvalue())) as package:
+            names = set(package.namelist())
+        assert "customXml/itemProps1.xml" not in names
+        assert "customXml/_rels/item1.xml.rels" not in names
+        assert "customXml/itemProps3.xml" in names
+        assert "customXml/_rels/item3.xml.rels" in names
+
+    def it_rejects_deleting_a_part_twice(self):
+        document = Document(io.BytesIO(FIXTURE.read_bytes()))
+        customers = _parts_by_name(document)["/customXml/item1.xml"]
+        document.part.delete_custom_xml_part(customers)
+
+        with pytest.raises(ValueError, match="is not related to this document"):
+            document.part.delete_custom_xml_part(customers)