Correct previous checkin, probably a svn merge issue.
Now the code is similar to the one in trunk/. The behavior was funny: >>> print (), repr(()) (), () >>> print (), repr(()) (), (...)
This commit is contained in:
parent
aa975432d4
commit
0f1653e957
|
@ -208,6 +208,10 @@ tuplerepr(PyTupleObject *v)
|
||||||
PyObject *s, *temp;
|
PyObject *s, *temp;
|
||||||
PyObject *pieces, *result = NULL;
|
PyObject *pieces, *result = NULL;
|
||||||
|
|
||||||
|
n = v->ob_size;
|
||||||
|
if (n == 0)
|
||||||
|
return PyString_FromString("()");
|
||||||
|
|
||||||
/* While not mutable, it is still possible to end up with a cycle in a
|
/* While not mutable, it is still possible to end up with a cycle in a
|
||||||
tuple through an object that stores itself within a tuple (and thus
|
tuple through an object that stores itself within a tuple (and thus
|
||||||
infinitely asks for the repr of itself). This should only be
|
infinitely asks for the repr of itself). This should only be
|
||||||
|
@ -217,10 +221,6 @@ tuplerepr(PyTupleObject *v)
|
||||||
return i > 0 ? PyString_FromString("(...)") : NULL;
|
return i > 0 ? PyString_FromString("(...)") : NULL;
|
||||||
}
|
}
|
||||||
|
|
||||||
n = v->ob_size;
|
|
||||||
if (n == 0)
|
|
||||||
return PyString_FromString("()");
|
|
||||||
|
|
||||||
pieces = PyTuple_New(n);
|
pieces = PyTuple_New(n);
|
||||||
if (pieces == NULL)
|
if (pieces == NULL)
|
||||||
return NULL;
|
return NULL;
|
||||||
|
|
Loading…
Reference in New Issue