[issue28526] Use PyUnicode_AsEncodedString instead of PyUnicode_AsEncodedObject

2016-10-27 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Thank you for your review Josh. -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 2.7 ___ Python tracker

[issue28526] Use PyUnicode_AsEncodedString instead of PyUnicode_AsEncodedObject

2016-10-27 Thread Roundup Robot
Roundup Robot added the comment: New changeset bea48e72cae5 by Serhiy Storchaka in branch '3.5': Issue #28526: Use PyUnicode_AsEncodedString() instead of https://hg.python.org/cpython/rev/bea48e72cae5 New changeset fe9f361f3751 by Serhiy Storchaka in branch '3.6': Issue #28526: Use PyUnicode_AsE

[issue28526] Use PyUnicode_AsEncodedString instead of PyUnicode_AsEncodedObject

2016-10-25 Thread Josh Rosenberg
Josh Rosenberg added the comment: LGTM. -- nosy: +josh.r ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue28526] Use PyUnicode_AsEncodedString instead of PyUnicode_AsEncodedObject

2016-10-25 Thread Serhiy Storchaka
New submission from Serhiy Storchaka: PyUnicode_AsEncodedObject() can return an object of arbitrary type, while PyUnicode_AsEncodedString() always returns bytes. The code that uses PyUnicode_AsEncodedObject() in the _curses module expects bytes, but does not check the type of the result. This