[issue8727] test_import failure

Barry A. Warsaw added the comment: r81290 -- assignee: brett.cannon -> barry resolution: -> fixed status: open -> closed ___ Python tracker ___ _

[issue8727] test_import failure

Barry A. Warsaw added the comment: Thanks, Antoine filled me in on IRC just before my 'net connection went down for many hours. The good news is that I have a fix for this and will commit it in a little while. -- ___ Python tracker

[issue8727] test_import failure

Brett Cannon added the comment: Sorry about that. I guess I should have been more explicit when I said that "I have flagged the test as an expected failure" that meant I made it pass in the test suite until I get a chance to fix this. -- ___ Python

[issue8727] test_import failure

Nick Coghlan added the comment: Brett marked it as an expected failure in r81219. Probably should have mentioned that here at the time though... -- ___ Python tracker ___ __

[issue8727] test_import failure

Barry A. Warsaw added the comment: I cannot reproduce this on Ubuntu 10.04 with current py3k (r81268), even using the boiled down example given by Antoine. What platform are you on? -- ___ Python tracker

[issue8727] test_import failure

Changes by Brett Cannon : -- priority: normal -> critical ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:/

[issue8727] test_import failure

Brett Cannon added the comment: I found the cause of the failure. When Barry implemented PEP 3147, he made PyPycLoader.bytecode_path() operate as if the only possible bytecode file one would want is the __cached__ one. That obviously is not accurate in the face of source-less modules. So the

[issue8727] test_import failure

Brett Cannon added the comment: THe sys.path modification warning is a red herring; the test simply was not cleaning up after itself properly. That little bit is fixed in r81214. Don't know about the cause of the actual failure yet. -- ___ Python

[issue8727] test_import failure

Antoine Pitrou added the comment: This can be narrowed down to the following test sequence: $ ./python -E -m test.regrtest test_heapq test_import test_heapq test_import Warning -- sys.path was modified by test_import test test_import failed -- Traceback (most recent call last): File "/home/an

[issue8727] test_import failure

New submission from Antoine Pitrou : [...] test_import Warning -- sys.path was modified by test_import test test_import failed -- Traceback (most recent call last): File "/home/antoine/py3k/__svn__/Lib/test/test_import.py", line 167, in test_module_with_large_stack exec('import ' + module)