Hi,
I need to embed an user-supplied python function body in a C program.
That is, the user has no control over the function definition:
def afunction():
Now, the problem is that I can't just append the supplied string,
because I need to properly indent it which isn't trivial - just adding
a
I suggest we keep focused on the main issue here, which is "shoud non-
ascii identifiers be allowed, given that we already allow non-ascii
strings literals and comments?"
Most arguments against this proposal really fall into the category
"ascii-only source files". If you want to promote code-shari
On 13 Mag, 17:44, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> - should non-ASCII identifiers be supported? why?
Yes. For the same reason non-ASCII source files are supported.
> - would you use them if it was possible to do so? in what cases?
Yes. In the same cases I'd use:
1) non-English comm
On 15 Mag, 15:44, George Sakkis <[EMAIL PROTECTED]> wrote:
> After 175 replies (and counting), the only thing that is clear is the
> controversy around this PEP. Most people are very strong for or
> against it, with little middle ground in between. I'm not saying that
> every change must meet 100%
