Ubuntu
python-qt4 package

python-qt4-doc examples do not work

Bug #462895 reported by sipiatti
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
python-qt4 (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: python-qt4

The most of the python-qt4 examples in Karmic (RC) do not work. They want to import a modul with the same name of them with an '_rc' at the end. But these files are missing.
Example:
qtdemo.py wants to import qtdemo_rc
systray.py wants to import systray_rc
etc.

package: python-qt4-doc-4.6-1

Revision history for this message
Philip Muškovac (yofel) wrote :

Seems like a few things were missed when packaging the examples.
For qtdemo and systray the resource files aren't compiled and an xml file that is needed by qtdemo is gzipped.
so to fix qtdemo you need to unzip qtdemo/xml/examples.xml.gz and run
pyrcc4 -o qtdemo_rc.py qtdemo.qrc
to fix systray you need to run
pyrcc4 -o systray_rc.py systray.qrc

Note: pyrcc4 is part of the pyqt4-dev-tools package

Changed in python-qt4 (Ubuntu):
status: New → Confirmed
Revision history for this message
Philip Muškovac (yofel) wrote :

Actually find finds 29 .qrc files in the examples that need to be compiled first to be used.

Revision history for this message
Micah Gersten (micahg) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as Triaged and let them handle it from here. Thanks for taking the time to make Ubuntu better! Please report any other issues you may find.

Changed in python-qt4 (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
Revision history for this message
alr (alrhodes) wrote :

Here's a small shell script to fix them all.

Cheers!

Revision history for this message
Olivier Berten (olivier-berten) wrote :

This is still needed in Maverick...

Revision history for this message
Scott Kitterman (kitterman) wrote :

I think what's needed here is a README to explain how to compile/run the demos. I think that they are reasonable as they are (files compressed to save space), but it ought to be clearer how to manage running them if needed. I probably won't have time to write such a README, but would be glad to add it to the package if someone else does.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.