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 eryksun
Recipients eryksun, ezio.melotti, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2018-01-15.15:22:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1516029730.24.0.467229070634.issue32556@psf.upfronthosting.co.za>
In-reply-to
Content
In issue 26330 it was noted that nt._getdiskusage doesn't accept bytes paths. The same applies to nt._getvolumepathname and nt._getfinalpathname. Callers of these functions shouldn't have to manually implement PEP 529 UTF-8 support to handle input and output bytes paths. 

On the other hand, nt._getfullpathname works with a bytes path since it takes a `path_t` argument instead of `unicode` or `Py_UNICODE`. The above 3 functions could be rewritten to use `path_t` for the input path, and then encode the output path via PyUnicode_EncodeFSDefault if path->narrow is set.
History
Date User Action Args
2018-01-15 15:22:10eryksunsetrecipients: + eryksun, paul.moore, vstinner, tim.golden, ezio.melotti, zach.ware, steve.dower
2018-01-15 15:22:10eryksunsetmessageid: <1516029730.24.0.467229070634.issue32556@psf.upfronthosting.co.za>
2018-01-15 15:22:10eryksunlinkissue32556 messages
2018-01-15 15:22:10eryksuncreate