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.

classification
Title: Carbon.CF.CFString should require ASCII
Type: Stage:
Components: macOS Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: jackjansen Nosy List: jackjansen, jvr
Priority: normal Keywords:

Created on 2003-02-07 09:35 by jackjansen, last changed 2022-04-10 16:06 by admin. This issue is now closed.

Messages (3)
msg14495 - (view) Author: Jack Jansen (jackjansen) * (Python committer) Date: 2003-02-07 09:35
If a Python string is passed where a CFString is expected the bytes are used verbatim (using CFStringCreateWithCString()), but this is probably wrong. We should either allow only ASCII or use sys.getdefaultencoding() or something similar.

This is a copy of PyObjC bug <https://sourceforge.net/tracker/?func=detail&atid=114534&aid=681880&group_id=14534>.
msg14496 - (view) Author: Just van Rossum (jvr) * (Python triager) Date: 2003-02-07 15:14
Logged In: YES 
user_id=92689

You can strike the "probably". Although the rest of Python uses the default encoding, I think it's actually wise to just use ASCII and nudge them towards unicode.
msg14497 - (view) Author: Jack Jansen (jackjansen) * (Python committer) Date: 2003-03-03 13:30
Logged In: YES 
user_id=45365

Implemented in CVS.
History
Date User Action Args
2022-04-10 16:06:37adminsetgithub: 37930
2003-02-07 09:35:21jackjansencreate