[PyQt] Python bindings for Poppler-Qt4, pypoppler-qt4

NARCISO, Rui RUI.NARCISO at airbus.com
Thu Dec 3 15:23:39 GMT 2009

Hi Wilbert

I'm very much interested on your approach so please keep us updated on your progress.


-----Message d'origine-----
De : pyqt-bounces at riverbankcomputing.com
[mailto:pyqt-bounces at riverbankcomputing.com]De la part de Wilbert
Envoyé : jeudi 3 décembre 2009 16:15
À : pyqt at riverbankcomputing.com
Objet : Re: [PyQt] Python bindings for Poppler-Qt4, pypoppler-qt4

Op donderdag 03 december 2009 schreef Rajeev:

> It doesnt have much to do with distributions, because these projects
> are doing it for their own needs and not for their distributions.

I meant that python-poppler-qt4 could become a package in the Linux 
distribution sense, and that other programs could simply depend om that 
package, instead of including (some fork of) it in their own source tarball.

I write and distribute a free software application (written in Python, called 
Frescobaldi, see www.frescobaldi.org ). In the future I want to extend that 
app with a PDF widget based on libpoppler-qt4. But I would rather not include 
the Python binding with my program (as it requires users to compile code).

Users should install the python binding separately. Other projects also can 
then depend on that package instead of including their own version.

But for the binding to be useful for others, the API coverage would need to be 
completed.  I for myself need the links() method of the Page object and the 
various Link* classes, but I would be willing to make the binding complete and 
cover and test the full API of libpoppler-qt4.

Then the binding could be released as tarballs so that other people can easily 
install it and (Linux) distributions can include packaged versions of the 
Python binding for libpoppler-qt4.

> Why do you need a fork on googlecode ? You can simply checkout on your
> local, make mods and send me patches. But if its really necessary, I
> can move it off Pardus' SVN repo and put it on Bitbucket.

I would rather not create a fork. If I can contribute patches it's good as 

My main reason for creating a (googlecode) repo, is that it would make it 
easier for me to work on both my machines and commit to the repo often. And to 
have a well-known place to provide source tarballs I can point users of my 
application to.

Best regards,
Wilbert Berendsen

"You must be the change you wish to see in the world."
        -- Mahatma Gandhi
PyQt mailing list    PyQt at riverbankcomputing.com

This mail has originated outside your organization, either from an external partner or the Global Internet.
Keep this in mind if you answer this message.

The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised.
If you are not the intended recipient, please notify Airbus immediately and delete this e-mail.
Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately.
All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.

More information about the PyQt mailing list