Fred Wright via devel <devel@ntpsec.org>: > BTW, all the tests fail on FreeBSD, due to an undefined reference in > jigs.py.
Huh? If so, why has this not shown up in the results from the FreeBSD buildbot. > Indeed. When I started looking at the ntpq bug, I noticed that there > seemed to be some inconsistencies in whether 'response' was expected to be > str or bytes. It doesn't matter in Python 2, of course. But tossing in > enough polystr() and polybytes() calls to make the exceptions go away > isn't necessarily the best approach to making reliable code. :-) Unfortunately it's about the only recourse we have. See http://www.catb.org/esr/faqs/practical-python-porting/ for detailed discussion. -- <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a> My work is funded by the Internet Civil Engineering Institute: https://icei.org Please visit their site and donate: the civilization you save might be your own. _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
