Opening issues without PDF files/MCVEs

[stefan6419846]

Inside our README we have the following section for quite some time:

A good bug ticket includes a MCVE - a minimal complete verifiable example. For pypdf, this means that you must upload a PDF that causes the bug to occur as well as the code you're executing with all of the output.

Additionally, the issue template specifically asks for executable code and a PDF file that reproduces the issue.

While we understand that such PDF files may contain private or internal content, and that creating a generic/clean reproducer is more challenging, these files are essential for properly analyzing the issue. We acknowledge that you are using our library and are interested in getting issues resolved. However, we dedicate a considerable amount of time to maintain and improve this project. Receiving incomplete reports in these cases is frustrating.

For this reason, we will close issues that cannot be reproduced due to the absence of an MCVE. The same action will be taken for pull requests where a corresponding test is missing.

If you encounter issues with files that you cannot publish directly, and if you are not familiar enough with the PDF syntax, you can either send the file as an attachment in an email to the maintainers, or attempt to find a suitable example to work on in the existing test files. Please note that emailing should be considered a last resort, as this method is specific to one person and does not enable other interested contributors to work on this.