Andres Petralli added the comment:
Re: rarity. There is at least one more person that ran into the same issue as
seen in this report: https://github.com/Azure/azure-cli/issues/5184
--
___
Python tracker
<https://bugs.python.org/issue32
Andres Petralli added the comment:
Moving doesn't work, but even removing the firewire adapter (which was unused
on my system), doesn't remove it from the output of ifconfig.
I did however work around the issue by just patching up uuid in a suboptimal
manner (truncated the 64bit in
Andres Petralli added the comment:
This could be purely incidental to have shown up in 10.13, but yes, the problem
comes from the fact that the first hardware ID in the list of devices happens
to be an EUI-64 address with 64 bits now. This is the Firewire interface of my
Mac Pro and maybe
Andres Petralli added the comment:
Here's the output from my system. This is a Mac Pro with a firewire port. Looks
as if the address was picked up from fw0: actually, not lo0. Guess _find_mac
just iterates until it hits a matching word for a hw address:
lo0: flags=8049 mtu
New submission from Andres Petralli :
uuid.py is getting a 64 bit hardware address for the loopback adapter in High
Sierra, specifically in _ifconfig_getnode(). The function expects a 48 bit mac
address, but is instead getting 64 bits back and converting it to an int value
that is too long
