This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author amaury.forgeotdarc
Recipients amaury.forgeotdarc, benjamin.peterson, dabeaz, jsafrane, pitrou
Date 2013-05-07.15:54:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1367942056.28.0.645884795017.issue17922@psf.upfronthosting.co.za>
In-reply-to
Content
Python remembers SWIG types because SWIG generates code like this:

PyTypeObject * SwigPyObject_TypeOnce(void) {
  static PyTypeObject swigpyobject_type;
  static int type_init = 0;
  if (!type_init) {
    // ... initialization code ...
    swigpyobject_type = tmp;
    type_init = 1;
    if (PyType_Ready(&swigpyobject_type) < 0)
      return NULL;
  }
}

SWIG should reset "type_init" on a fresh interpreter.
The initXxx() function should do this.
History
Date User Action Args
2013-05-07 15:54:16amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, pitrou, benjamin.peterson, dabeaz, jsafrane
2013-05-07 15:54:16amaury.forgeotdarcsetmessageid: <1367942056.28.0.645884795017.issue17922@psf.upfronthosting.co.za>
2013-05-07 15:54:16amaury.forgeotdarclinkissue17922 messages
2013-05-07 15:54:16amaury.forgeotdarccreate