artemp/mapnik — Issue #398: Don't register fonts and plugins on module initialization
Author: artemp
Created: 2011-10-11 16:16:29+00:00
State: open
Labels: Boost_Python_Binding

Current implementation of __init__.py has a side effect: it registers fonts when being imported. The same is being done for plugins. I fail to see why this [implicit] method was chosen over [explicitely] creating separate functions for that.
Also, as a side note, DatasourceCache and FontEngine classes don't have ways of unregistering plugin/font which lead to several not-so-evident bugs in our code. I think this issue deserves its own entry in the tracker. :)