Stefan Behnel added the comment: 1) Is this reproducible?
2) Getting a crash in compile.c indicates that this is happening at parse/compile time and not when your Python code is executing. Can you confirm that? Does it generate a .pyc file on import that would indicate a successful byte code compilation? If it's a compiler issue, then the dependencies won't actually matter. 2) Is the code position where the crash happens (in dfs()) predictable, or does it vary across multiple runs? 3) Does this appear to be specific to Windows, or can you reproduce it on other platforms, too? And yes, seeing the file would be helpful. Could you at least compress it and make it available on the web somewhere for now? ---------- nosy: +scoder _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue31113> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
