Staging
v0.5.1
v0.5.1
Revision 54fb1b9864f143c6f30b6a5bb83c2b6465ce8fde authored by Mads Kiilerich on 13 August 2019, 10:51:39 UTC, committed by Mads Kiilerich on 13 August 2019, 10:51:39 UTC
pyrcc4 might be run at runtime if resources seem out of date. That is a bit of hack, hopefully only used during development. pyrcc4 might not be available if development isn't installed. Make it explicit that something is outdated and we "have" to run it. Also when running it properly from setup.py, the error message could disappear in the long log. Make sure to report failures loud and clear, and make a brutal exit. setup.py will now fail like: Resource files are outdated, ran: ['pyrcc4', 'hgviewlib/qt4/hgqv.qrc', '-o', 'build/lib/hgviewlib/qt4/hgqv_rc.py'] pyrcc4 failed: [Errno 2] No such file or directory Failure at runtime will look like: Resource files are outdated, running: pyrcc4 /home/mk/hgview/hgviewlib/qt4/hgqv.qrc -o /home/mk/hgview/hgviewlib/qt4/hgqv_rc.py sh: pyrcc4: command not found ERROR: Cannot convert the resource file '/home/mk/hgview/hgviewlib/qt4/hgqv.qrc' into a python module. Please check the PyQt 'pyrcc4' tool is installed, or do it by hand running
1 parent 101447d
File | Mode | Size |
---|---|---|
bin | ||
debian | ||
doc | ||
hgext3rd | ||
hgviewlib | ||
.hgignore | -rw-r--r-- | 49 bytes |
.hgtags | -rw-r--r-- | 3.4 KB |
COPYING | -rw-r--r-- | 17.6 KB |
ChangeLog | -rw-r--r-- | 5.7 KB |
MANIFEST.in | -rw-r--r-- | 704 bytes |
README | -rw-r--r-- | 1.8 KB |
__pkginfo__.py | l--------- | 24 bytes |
setup.py | -rw-r--r-- | 14.4 KB |
Computing file changes ...