Hi Bob :) After I upgraded dnspython from 1.6 to 1.7.1 on my NetBSD system, a script that had previously enjoyed excellent performance started taking a very long and unpredictable time to execute.
It turned out "import dns.message" was taking a long time because it was exhausting the entropy in /dev/random and blocking. It would probably be better to use /dev/urandom instead of /dev/random on systems that make the distinction to avoid this. It's really confusing because there is no diagnostic; things just stop or slow to a crawl. It would also be nice if dnspython didn't read from the random device until you perform an operation that actually needs entropy, like constructing a message to send; it shouldn't be a side effect of importing the module. Best regards, -- Andreas Gustafsson, [email protected] _______________________________________________ dnspython-bugs mailing list [email protected] http://howl.play-bow.org/mailman/listinfo.cgi/dnspython-bugs
