BIND 10 #312: python msgq timeouts differ from c++ ones

BIND 10 Development do-not-reply at isc.org
Wed Aug 18 15:25:17 UTC 2010


#312: python msgq timeouts differ from c++ ones
---------------------+------------------------------------------------------
  Reporter:  jelte   |            Owner:                      
      Type:  defect  |           Status:  new                 
  Priority:  major   |        Milestone:  y2 6 month milestone
 Component:  msgq    |         Keywords:                      
 Sensitive:  0       |   Estimatedhours:  0                   
     Hours:  0       |         Billable:  1                   
Totalhours:  0       |         Internal:  0                   
---------------------+------------------------------------------------------
 In the python msgq/cc api, when a blocking read times out, it results in a
 (env, msg) = (None, None) result. But the c++ version currently raises an
 exception. The python API should probably do the same.

 This also means catching it in the right places in the modules, if
 necessary (which is the reason it was left as it is in #296).

-- 
Ticket URL: <http://bind10.isc.org/ticket/312>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list