fix: filter coordinates kwargs to prevent TypeError in hi_res PDF processing #4206
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes a bug where passing
coordinates=Truetopartition()causes a TypeError when processing PDFs with the hi_res strategy.Problem
When users call
partition()withcoordinates=True, the boolean value flows through kwargs and eventually reachesadd_element_metadata(). However, this function already receives computed coordinate data as an explicit parameter. Python then raises:This is confusing because users reasonably expect
coordinates=Trueto enable coordinate output, not realizing that hi_res strategy already computes and includes coordinates automatically.Solution
Filter out
coordinatesandcoordinate_systemfrom kwargs before passing them toadd_element_metadata(). This prevents the conflict while preserving the internally-computed coordinate data.The fix is minimal and targeted - just 3 lines of code that filter the problematic kwargs.
Changes
unstructured/partition/pdf.py: Added filtering forcoordinatesandcoordinate_systemkwargsCHANGELOG.md: Added entry for this fixFixes #4126