I have embedded python3.3 in my application.
I got a crash when I ran a python script containing sample TK window creation code in it.
 
On interpreter shutdown, all strings are released (through _PyUnicode_ClearStaticStrings). (I Found this description in one of the comments of object.h header file)
 
When I tried to debug python source, I found a defect in _PyUnicode_ClearStaticStrings() method.
 
Existing function definition in python3.3 source (unicodeobject.c) is as follows

void _PyUnicode_ClearStaticStrings()
{
     _Py_Identifier *i;
      for (i = static_strings; i; i = i->next) {
           Py_DECREF(i->object);
           i->object = NULL;
           i->next = NULL;
      }
}
 
Here, for loop will not free all the static strings. It will free only the first static string in the list.
This loop needs to be corrected.
 
I corrected the loop in following way and its working fine for me.
 
void _PyUnicode_ClearStaticStrings()
{
    _Py_Identifier *i;
    while(static_strings->next != NULL)
    {
        i = static_strings;
        static_strings = static_strings->next;
        Py_DECREF(i->object);
        i->object = NULL;
        i->next = NULL;
    }
   
    Py_DECREF(static_strings->object);
    static_strings->object = NULL;
    static_strings = NULL;
}
 
Is this a bug or it is done so intentionally..?

It's a bug; thanks for pointing this out. I always suspected that there was something wrong, but never found the time to look into it.

When are you planning to submit a fix for it..? This bug will be fixed in python3.3 and a new version of python3.3 will be released..? Or it will be fixed in python3.4..?

New changeset 3e18ccaa537e by Benjamin Peterson in branch '3.3':
correct static string clearing loop (closes #16906)
http://hg.python.org/cpython/rev/3e18ccaa537e

New changeset 0c04ed40eeaf by Benjamin Peterson in branch 'default':
merge 3.3 (#16906)
http://hg.python.org/cpython/rev/0c04ed40eeaf