[issue3812] py3k build fails if configure --without-threads

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: Thanks, fixed in r66340(py3k). -- resolution: accepted -> fixed status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> _

[issue3812] py3k build fails if configure --without-threads

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Agreed. I suggest that you add a comment like "itertools.chain is in an extension module and may be unavailable" just above. Otherwise, someday one will find that this code should use a function from the stdlib, and revert your change...

[issue3812] py3k build fails if configure --without-threads

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: Simple workaround is to remove itertools from traceback module and write equivalent code to itertools.chain. I'm not sure it is acceptable put such limitation to standard library. (That is, traceback is used from build process, so should n

[issue3812] py3k build fails if configure --without-threads

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: Sorry, I removed workaround patch. It was not simply working.:-( ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3812] py3k build fails if configure --without-threads

Changes by Hirokazu Yamamoto <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file11430/py3k_workaround.patch ___ Python tracker <[EMAIL PROTECTED]> ___ __

[issue3812] py3k build fails if configure --without-threads

New submission from Hirokazu Yamamoto <[EMAIL PROTECTED]>: Hello. I failed to build py3k on cygwin (configure --without-threads). It's because io.py imports _dummy_thread, and it imports traceback, and it tries to import c-module itertools which is not built yet. Attached file is workaround patc