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 ncoghlan
Recipients Arfrever, eric.snow, georg.brandl, ncoghlan, serhiy.storchaka, vstinner
Date 2013-11-20.14:13:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1384956837.86.0.540271421301.issue19518@psf.upfronthosting.co.za>
In-reply-to
Content
Perhaps we could we use the suffix "Unicode" rather than "Object"? These don't work with arbitrary objects, they expect a unicode string.

PyRun_InteractiveOneObject would be updated to use the new suffix as well.

That would both be clearer for the user, and address Serhiy's concern about the possible ambiguity: PyRun_FileUnicode still isn't crystal clear, but it's clearer than PyRun_FileObject.
History
Date User Action Args
2013-11-20 14:13:57ncoghlansetrecipients: + ncoghlan, georg.brandl, vstinner, Arfrever, eric.snow, serhiy.storchaka
2013-11-20 14:13:57ncoghlansetmessageid: <1384956837.86.0.540271421301.issue19518@psf.upfronthosting.co.za>
2013-11-20 14:13:57ncoghlanlinkissue19518 messages
2013-11-20 14:13:57ncoghlancreate