This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients OG7, christian.heimes, gregory.p.smith, meiermic, nadeem.vawda, pitrou, python-dev, vstinner
Date 2011-05-17.19:50:41
SpamBayes Score 0.00012906948
Marked as misclassified No
Message-id <1305661842.62.0.896965305791.issue1746656@psf.upfronthosting.co.za>
In-reply-to
Content
Sorry to reopen, but do these methods really have to return *byte strings* for interface names?
In Python 3, we usually take the position that textually meaningful data should be str, not bytes (even filenames under POSIX). The usual way to do this is to use the "filesystem encoding" (os.fsdecode in pure Python, PyUnicode_DecodeFSDefault in C).

Also, the tests are really minimal. They should at least check the type and structure of values returned by these functions.
History
Date User Action Args
2011-05-17 19:50:42pitrousetrecipients: + pitrou, gregory.p.smith, vstinner, christian.heimes, OG7, meiermic, nadeem.vawda, python-dev
2011-05-17 19:50:42pitrousetmessageid: <1305661842.62.0.896965305791.issue1746656@psf.upfronthosting.co.za>
2011-05-17 19:50:42pitroulinkissue1746656 messages
2011-05-17 19:50:41pitroucreate