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 fhamand
Recipients fhamand
Date 2013-04-08.22:55:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365461726.69.0.844789226325.issue17669@psf.upfronthosting.co.za>
In-reply-to
Content
I've found a very strange bug in python 3.3

It's taken me around an hour just to narrow it down to a small case where it happens.

I cannot for the life of me figure out the exact cause. It seems to have something to do with "yield from".

I've attached a case which reproduces this. Run python3.3 test.py, it should segfault on linux, "stopped responding" on windows.

Tested with
OS: Linux Debian-60-squeeze-32-minimal 2.6.32-5-686-bigmem
PY: Python 3.3.1rc1 (default, Mar 30 2013, 21:44:39)

OS: Windows 7 64 bit
PY: Python 3.3.0 (v3.3.0:bd8afb90ebf2, Sep 29 2012, 10:55:48) [MSC v.1600 32 bit (Intel)] on win32


NOTES: If you get rid of "import logging" in generators.py, it only crashes if there's no __pycache__
History
Date User Action Args
2013-04-08 22:55:26fhamandsetrecipients: + fhamand
2013-04-08 22:55:26fhamandsetmessageid: <1365461726.69.0.844789226325.issue17669@psf.upfronthosting.co.za>
2013-04-08 22:55:26fhamandlinkissue17669 messages
2013-04-08 22:55:26fhamandcreate