BIND 10 #1274: config_plugins installation location and python byte compilation

[BIND 10 Development]

#1274: config_plugins installation location and python byte compilation
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  New Tasks
                   Priority:  minor  |            Resolution:
                  Component:         |             Sensitive:  0
  Unclassified                       |           Sub-Project:  Core
                   Keywords:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by vorner):

 Hello

 Replying to [ticket:1274 jreed]:
 > At first I thought the location was wrong since "share" is for
 "architecture-independent text files". But shane tells me they are machine
 independent. But they are python version dependent, so since it should be
 python3.1 identified that maybe keeping under normal python versioned
 site-packages is better. Is it okay to keep non-python modules (like our
 config_plugins) under normal site-packages location?

 First, to correct something slightly. They are python, but not modules.
 Or, not modules in the usual sense, they, in theory, could be used as
 modules.

 But if somebody accidentally used them as modules, he would be probably
 surprised. So I wouldn't like to have them somewhere an import could find
 them by itself.

 Also, the plugin-loading machinery just goes through a directory and loads
 everything it finds there. So nothing else should get into that place
 also.

 Otherwise, I don't really care about where they live, if the config
 manager can know it by itself at startup.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1274#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development