BIND 10 #2742: Fatal Python error: Py_Initialize: can't initialize sys standard streams

[BIND 10 Development]

#2742: Fatal Python error: Py_Initialize: can't initialize sys standard streams
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:
            Priority:  medium        |  closed
           Component:  loadzone      |                    Milestone:
            Keywords:                |  Sprint-20130305
           Sensitive:  0             |                   Resolution:  fixed
         Sub-Project:  DNS           |                 CVSS Scoring:
Estimated Difficulty:  3             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by jelte):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 More info:

 From a quick look at the code the general maximum accepted length is the
 systems MAXPATHLEN define; which is 4096 on my linux machine, but 1024 on
 my freebsd. This is not specific to python 3.1, but seems related to OS-
 specific initialization code in python (it happens with 3.2 as well).

 I noticed different behaviour here though; if I make PYTHONPATH exceed
 4096 it'll just remove entries, but not crash.

 We can't really do anything about this in our code except not exceed that
 in our test environment. We could file a bug but it may be too out-there
 to address.

 So I'm wrapping this up and closing the ticket.

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