'''
Upon execution of a rule set, a subject is evaluated by each rule in order.

When the rule is based on a processor, the processor returns a modified subject. 
Optionally a processor reports according to the `report_template` given in the rule.

The report_template can be a simple string or a string where parameters 
will be substituted with a value generated by the processor. 
The documentation of the processor should explain which parameters should be inserted how.

Using the standard Markdown reporter the strings reported support Markdown. Other reporters might support something different. 
Documentation of the reporter should clarify that.

In the documentation of each processors is referred to a "definition". This is the rule as written in the rule_set.

In the documentation of each processors is referred to a "subject". A processor will modify this subject according to the rule. 
The processor will ignore any parameters in this subject which is not needed for this particular processor. 
So the examples given illustrate which parameters need to be included for the documented processor. 
In real life more parameters will be present in a subject.

'''

# first import all processors dependent on python libraries needed by geoDSS only.

from ..processors import    alter_key, \
                            bag_geocoder, \
                            pdok_locatieserver, \
                            random_point_geometry, \
                            random_value

# then try to import other processors as well; skip a processor if import fails.

try:
    from ..processors import postgis_processing
except:
    pass

try:
    from ..processors import postgis_unit_test
except:
    pass

try:
    from ..processors import ogr_processing
except:
    pass

# and as long as we are developing we try the import here to prevent exceptions being caught.
from ..processors import alter_key_xpath