Author eryksun
Recipients Segev Finer, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2017-12-19.05:44:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1513662249.68.0.213398074469.issue32370@psf.upfronthosting.co.za>
In-reply-to
Content
ipconfig uses (or defaults to) OEM encoded output when writing to a pipe or file. On the other hand, Python's TextIOWrapper defaults to ANSI (i.e. 'mbcs'). In 3.6+, uuid._ipconfig_getnode could be rewritten to call subprocess.Popen with the new 'oem' encoding. 

In Windows 10, the networking command-line utilities (e.g. ipconfig, netstat, nbtstat, ping, tracert, hostname, finger, and ftp) support an "OutputEncoding" environment variable. Its value can be set to "Unicode" (UTF-16), "UTF-8", or "Ansi". I don't think this is supported in Windows 7, however.
History
Date User Action Args
2017-12-19 05:44:09eryksunsetrecipients: + eryksun, paul.moore, tim.golden, zach.ware, steve.dower, Segev Finer
2017-12-19 05:44:09eryksunsetmessageid: <1513662249.68.0.213398074469.issue32370@psf.upfronthosting.co.za>
2017-12-19 05:44:09eryksunlinkissue32370 messages
2017-12-19 05:44:09eryksuncreate