On Mon, Apr 30, 2012 at 6:57 PM, Senthil Kumaran wrote: > Irrespective of this - Issue13183 seems to be an easy to verify bug in > 3.2 and 3.3. I think, it would most visible if you were to use a full > screen debugger and you will notice that the return call indicator has > jumped to the next statement (skipping return) when returning. I > guess, that's why Xavier (pyclewn author) noted it. The fix seems > fine too. > > I have just requested an additional info and this particular one could > be fixed.
Thanks for your help on this issue Senthil. Xavier _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
