Message152791
| Author |
Jim.Jewett |
| Recipients |
Jim.Jewett, ezio.melotti, loewis, vstinner |
| Date |
2012年02月06日.22:08:41 |
| SpamBayes Score |
2.1825097e-06 |
| Marked as misclassified |
No |
| Message-id |
<CA+OGgf6-K=++iaV81V3LHtuZVSCrgktm0V3cREY6PjH3VgUXrQ@mail.gmail.com> |
| In-reply-to |
<1328563507.3.0.111429381653.issue13958@psf.upfronthosting.co.za> |
| Content |
On Mon, Feb 6, 2012 at 4:25 PM, Martin v. Löwis <report@bugs.python.org> wrote:
> Martin v. Löwis <martin@v.loewis.de> added the comment:
> This has nothing to do with PEP 3131. Python could (and does)
> support non-ASCII identifiers just fine, regardless of C compiler
> limitations.
I *think* you're saying that the _Py_Identifier( ) is a smaller set
than identifiers in general. Would the following be more accurate?
/* PEP3131 does allow non-ASCII identifiers in user code, but
limits their use within the implementation itself.
In particular, a _Py_Identifier may be passed directly to
C code; such identifiers are restricted to ASCII to avoid
breaking some supported C compilers. */ |
|