➜

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 xiang.zhang
Recipients berker.peksag, docs@python, vstinner, xiang.zhang
Date 2016-08-19.15:55:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1471622138.29.0.706692992163.issue27740@psf.upfronthosting.co.za>
In-reply-to
Content 
> filename is going to be decoded inside of Py_CompileStringExFlags

Actually all I want to express is this, *filename* will be decoded inside. But now the wording looks to me is that *filename* is already a decoded string when passed. I don't want to document anything about PyUnicode_EncodeFSDefault. I should remove (:func:`os.fsdecode`). How do you think? I'm Okay if you think the current wording is correct.
History
Date User Action Args
2016-08-19 15:55:38xiang.zhangsetrecipients: + xiang.zhang, vstinner, docs@python, berker.peksag
2016-08-19 15:55:38xiang.zhangsetmessageid: <1471622138.29.0.706692992163.issue27740@psf.upfronthosting.co.za>
2016-08-19 15:55:38xiang.zhanglinkissue27740 messages
2016-08-19 15:55:38xiang.zhangcreate