Skip to content

Conversation

@olf42
Copy link
Contributor

@olf42 olf42 commented Feb 27, 2020

I removed the gobject dependency. I feel like this removes a lot of pain, as PyMuPDF is self-contained, and we now only have dependencies that are installable via pip.

Now the latest version of Python is used in the Dockerfile (3.8.1-buster).

cfra and others added 8 commits November 10, 2017 22:31
Tested with Python3.8.1
__cmp__ is not respected in Python 3, therefore a TypeError is
raised in L215 in read_layers.py when it is attempted to sort
the layers.

This was fixed by renaming the __cmp__ method to __lt__.
We now use python:3.8.1-buster as baseimage. Without the gobject
dependency we can use the latest python version, without running
into trouble to not find the gobject bindings for that version.

This also allows us, to use the latest version of pymupdf, as
the only available wheel for buster default python 3.7.3 was
1.16.6. Now: 1.16.11
Copy link
Owner

@cfra cfra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you very much for this contribution towards cleaning up the requirements. 🙂

I have tested out this branch and discovered a few shortcomings with it which need to be fixed before it can go in:

  • to ensure fonts remain readable, PDFs need to be rendered at the scale applicable for each tile,
    just rendering the PDF once and resizing it for other zoom levels is unfortunately not an option
  • the new renderer doesn't seem to take inverted rendering and scaling/translation into account, at least some test layers which make use of these features yielded highly different results in the new renderer compared to the old renderer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants