It checks for ifconfig, /sbin/ifconfig, and /usr/sbin/ifconfig (same for arp). The problem is the os.pipe command doesn't hide these issues. It doesn't cause the test to fail, but is still broken. The test is presumably failing for the other reason I mentioned (unixdll_getnode). Let me know if you see that when running with -v.
n -- On 7/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I just tried building and testing 2.5 on a Solaris 10 box at work. The uuid > test failed with > > sh: ifconfig: not found > sh: ifconfig: not found > sh: ifconfig: not found > sh: arp: not found > sh: ifconfig: not found > sh: ifconfig: not found > sh: ifconfig: not found > sh: arp: not found > > In our environment at least it's uncommon for /usr/sbin to be in the PATH of > non-privileged users: > > piggy:% type -a ifconfig > -bash: type: ifconfig: not found > piggy:% PATH=$PATH:/usr/sbin type -a ifconfig > ifconfig is /usr/sbin/ifconfig > > Perhaps test_uuid needs to do a little investigation to find ifconfig and > arp. > > Skip > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/nnorwitz%40gmail.com > _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
