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.

classification
Title: test_heapq interfering with test_import on py3k
Type: behavior Stage: needs patch
Components: Tests Versions: Python 3.2
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: barry, brett.cannon, tim.golden
Priority: normal Keywords:

Created on 2010-04-18 13:13 by tim.golden, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
test_import.log tim.golden, 2010-04-18 13:13
Messages (2)
msg103488 - (view) Author: Tim Golden (tim.golden) * (Python committer) Date: 2010-04-18 13:13
If test_heapq is run before test_import on the current py3k head,
test_import will fail as per the attached traceback.

python -m test.regrtest -W test_heapq test_import > test_import.log

At a glance I can't see any obvious reason why test_heapq should have
any effect on test_import. Raising this bug while I try to narrow down.

An extra assert inside support.make_legacy_pyc confirms that
the .pyc being renamed into does in fact already exist.

Running test_import on its own or via regrtest when not preceded
by test_heapq runs with error.
msg108343 - (view) Author: Tim Golden (tim.golden) * (Python committer) Date: 2010-06-22 08:18
Error no longer occurs
History
Date User Action Args
2022-04-11 14:57:00adminsetgithub: 52687
2010-06-22 08:18:09tim.goldensetstatus: open -> closed
resolution: fixed
messages: + msg108343
2010-04-18 13:29:40pitrousetnosy: + barry, brett.cannon
versions: + Python 3.2
priority: normal
components: + Tests
type: behavior
stage: needs patch
2010-04-18 13:13:40tim.goldencreate