Movatterモバイル変換

[Python-Dev] Is this safe enough? Re: [Python-checkins] cpython: _Py_Identifier are always ASCII strings

• Previous message:[Python-Dev] Is this safe enough? Re: [Python-checkins] cpython: _Py_Identifier are always ASCII strings
• Next message:[Python-Dev] Is this safe enough? Re: [Python-checkins] cpython: _Py_Identifier are always ASCII strings
• Messages sorted by:[ date ][ thread ][ subject ][ author ]

> I would prefer to see _Py_Identifier renamed to _Py_ASCII_Identifier,> or at least a comment stating that Identifiers will (per PEP 3131)> always be ASCII -- preferably with an assert to back that up.Please ... no.This is a *convenience* interface, whose sole purpose is to make somethingmore convenient. Adding naming clutter destroys this objective.I'd rather restore support for allowing UTF-8 source here (I don't thinkthat requiring ASCII really improves much), than rename the macro.The ASCII requirement is actually more in the C compiler than in Python.Since not all of the C compilers that we compile Python with supportnon-ASCII identifiers, failure to comply to the ASCII requirement willtrigger a C compilation failure.Regards,Martin

• Previous message:[Python-Dev] Is this safe enough? Re: [Python-checkins] cpython: _Py_Identifier are always ASCII strings
• Next message:[Python-Dev] Is this safe enough? Re: [Python-checkins] cpython: _Py_Identifier are always ASCII strings
• Messages sorted by:[ date ][ thread ][ subject ][ author ]