Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fullcopypage bug #4043

Closed
cole-dda opened this issue Nov 12, 2024 · 5 comments
Closed

fullcopypage bug #4043

cole-dda opened this issue Nov 12, 2024 · 5 comments
Labels
bug fix developed release schedule to be determined Fixed in next release

Comments

@cole-dda
Copy link

Description of the bug

screenshot_6579

res may be bytes type ,so no "m_internal" attribute

How to reproduce the bug

x.pdf

import fitz
doc = fitz.open('x.pdf')
doc.fullcopy_page(0)

PyMuPDF version

1.24.13

Operating system

MacOS

Python version

3.12

@JorjMcKie
Copy link
Collaborator

Cannot confirm: Works for me on Linux and Windows, PyMuPDF 1.24.13 and 1.24.11.

@JorjMcKie
Copy link
Collaborator

You did not even mention what error happened by the way.

@cole-dda
Copy link
Author

cole-dda commented Nov 12, 2024

I'am sorry

    import fitz
    doc = fitz.open('x.pdf')
    doc.fullcopy_page(1)
screenshot_6582

@JorjMcKie
Copy link
Collaborator

This time yes.
This happens only if the duplicated page is empty (has no /Contents objects).
Easy fix.

@julian-smith-artifex-com
Copy link
Collaborator

Fixed in PyMuPDF-1.24.14.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug fix developed release schedule to be determined Fixed in next release
Projects
None yet
Development

No branches or pull requests

3 participants