GInga takes ages to load

(Python 3) When I start ginga, it shows a blank screen for ~30 seconds, before it is actually ready to go.

2018-03-15 10:25:15,976 | I | main.py:364 (main) | Chosen toolkit (qt5) family is 'qt'
2018-03-15 10:25:16,949 | D | Task.py:1012 (startall) | startall called
2018-03-15 10:25:16,949 | D | Task.py:1037 (startall) | starting threads in thread pool
2018-03-15 10:25:16,950 | D | Task.py:926 (taskloop) | Starting worker thread loop.
[...]
2018-03-15 10:25:52,975 | D | ImageView.py:1522 (get_rgb_object) | times: total=0.0047
2018-03-15 10:25:52,975 | D | ImageViewQt.py:172 (render_image) | redraw pixmap=<PyQt5.QtGui.QPixmap object 
2018-03-15 10:25:52,975 | D | ImageViewQt.py:175 (render_image) | drawing to pixmap
2018-03-15 10:25:52,975 | D | ImageViewQt.py:149 (_render_offscreen) | data shape is 664x664x4
2018-03-15 10:25:52,986 | D | ImageViewQt.py:252 (update_image) | updating window from pixmap
2018-03-15 10:25:52,986 | D | ImageView.py:1265 (redraw_now) | widget 'colorbar' redraw (whence=0) delta=0.0

The full log is attached. ginga.log

[olebole]

These are not the config files, but the examples. In Debian, examples belong to the package documentation and therefore should be located in /usr/share/doc/<<package>>/examples.

[pllim]

@olebole , what is the motivation for having the config files in usr/share/doc instead of using the ones that come with Ginga installation? They seem to be included by default when I check PyPI tarball.

Anyway, I don’t see problem for you to sed it in a way that works for Debian. Even if you don’t patch it, when generate_cfg_example() cannot find the file, it simply throws a warning and returns empty string, so you can simply comment out warnings.warn() in that function as well. The resultant incomplete docstring only affects offline help pages, which are never displayed unless you click “Help” when not connected to Internet.