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 scoder
Recipients Arfrever, amaury.forgeotdarc, pitrou, scoder, vstinner
Date 2010-01-31.07:39:06
SpamBayes Score 5.62006e-11
Marked as misclassified No
Message-id <1264923549.44.0.708477709826.issue7173@psf.upfronthosting.co.za>
In-reply-to
Content
Looks like this is one of those bugs that run away when you look too close...

I can get it to crash reliably for me with the latest py3k branch (and all Python 3.x release versions) when I run the test suite completely, so here's a new recipe. The intention is to keep CPython from importing Cython built modules to make sure it's not related to the C code that Cython generates. I thought it was when I hit this problem ages ago (1 or 2 years?), but I can now assure you, it's not. To reproduce, run:

    python3.2 runtests.py --no-cpp --no-pyregr --no-doctest \
          --no-fork --cython-only --no-refnanny -vv 'run\.'

The "--cython-only" switch makes sure the modules are not run through the C compiler, so no binary modules are built and only the pure Python code of the Cython compiler runs here. The output is a little badly formatted, but it basically prints the name of the modules it compiles and crashes after a while (also without the patch).

You don't have to do anything for cleanup, the test runner does that.

Writing a shorter code snippet is really not easy as there seem to be various things involved here, apparently including exception handling, recursion and generators.
History
Date User Action Args
2010-01-31 07:39:09scodersetrecipients: + scoder, amaury.forgeotdarc, pitrou, vstinner, Arfrever
2010-01-31 07:39:09scodersetmessageid: <1264923549.44.0.708477709826.issue7173@psf.upfronthosting.co.za>
2010-01-31 07:39:07scoderlinkissue7173 messages
2010-01-31 07:39:06scodercreate