Vitja Makarov, 06.11.2011 18:10:
When file encoding is specified cython generates two PyObject entries
for string consts one for the variable name and one for the string
constant.
That's because the content may actually become different after decoding,
even if the encoded byte sequence is identical. Note that decoding is only
done in Py3. In Py2, the byte sequence is used, so both values are identical.
Here is ticket: http://trac.cython.org/cython_trac/ticket/740
At the first time I thought that this is C++ related bug. Now I
realise that C doesn't complains about.
I bet there's the usual "yes, please really tell me what I'm doing wrong"
compiler option for that. "-Werrors" may do the trick at least.
Here is minimal example:
$ cat cplus.pyx
# -*- coding: koi8-r -*-
wtf = 'wtf'
Generaets the following code:
/* Implementation of 'cplus' */
static char __pyx_k__wtf[] = "wtf";
static char __pyx_k____main__[] = "__main__";
static char __pyx_k____test__[] = "__test__";
static PyObject *__pyx_n_s____main__;
static PyObject *__pyx_n_s____test__;
static PyObject *__pyx_n_s__wtf;
static PyObject *__pyx_n_s__wtf;
...
static __Pyx_StringTabEntry __pyx_string_tab[] = {
{&__pyx_n_s____main__, __pyx_k____main__, sizeof(__pyx_k____main__),
0, 0, 1, 1},
{&__pyx_n_s____test__, __pyx_k____test__, sizeof(__pyx_k____test__),
0, 0, 1, 1},
{&__pyx_n_s__wtf, __pyx_k__wtf, sizeof(__pyx_k__wtf), "koi8-r", 0, 1, 1},
{&__pyx_n_s__wtf, __pyx_k__wtf, sizeof(__pyx_k__wtf), 0, 0, 1, 1},
{0, 0, 0, 0, 0, 0, 0}
};
Both Python object variables should have different cnames.
Stefan
_______________________________________________
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
