Christian Heimes added the comment:
I've fixed the bug in Python 3.0 a few weeks ago. I'm not sure about the
stackless bug but this is the wrong place to report it. Please contact
the other Christian.
--
resolution: - invalid
status: open - closed
__
Christian Heimes added the comment:
Right, the Python bug tracker is not the place to report Stackless bugs.
But my tests have revealed a bug in Python 3.0. As today multiple
reinitialization still fails.
I suspect a reference bug but I can't proof it.
--
assignee: gvanrossum -
Christian Heimes added the comment:
I've added some debugging code to _Py_ForgetReference and now I'm
getting this:
$ ./reinit_test
round 1
[23832 refs]
round 2
[24558 refs]
round 3
* ob
object : refcnt 0 at 0x821d728
type: str
refcount: 0
address : 0x821d728
* op-_ob_prev-_ob_next
object
Guido van Rossum added the comment:
Note that the OP was complaining about Stackless. This is not the place
to report issues with that.
--
priority: normal - low
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1306
Christian Heimes added the comment:
Python 3.0 suffers from an problem with reinitialization but I can't
reproduce the bug with the release branch of 2.5. Python 2.6 also does
fine but leaks some references.
// reinit_test.c
#include Python.h
#define ROUNDS 5
int main(void) {
int i;
Christian Heimes added the comment:
The patch solves one issue. It resets the Py_DefaultFileSystemEncoding
to NULL when no default value was given. However the finalization fails
after the 3rd round at
if (op == refchain ||
op-_ob_prev-_ob_next != op || op-_ob_next-_ob_prev
New submission from Karemir:
Hi,
I'm embedding stackless python in a c++ application under linux. When I
try to Finalize and Initialize again, I'm getting errors. this is a
sample code that doesn't work:
int main() {
Py_Initialize();
Py_Finalize();
Py_Initialize();
