-
-
Notifications
You must be signed in to change notification settings - Fork 428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test failures on tip #337
Comments
Since I don't hear people complaining about the difference between "coverage run foo.py" and "python foo.py", I think we should change try_execfile.py to be resilient to these differences. If the extra/missing sys.path entries are actually just duplicate (symlinked) paths, then we can have our own function that reduces sys.path to the unique entries, keeping the order, and then compare those. |
Fixed in changeset 4f5a5a0b3466 (bb). Please let me know if there are still problems. |
And the fix is tweaked in 17f7fcc85836 (bb) |
I can confirm that these two commands repro the problem. |
(Would have been good to make a separate issue for the separate failures, but there's context here, so whatever :) |
If you're going to put work into this ticket, make a new one. Now there's a changeset referencing this ticket, and the thing it fixes bears no relation to the title of the ticket. :( |
back to fixed. |
Originally reported by Buck Evan (Bitbucket: bukzor, GitHub: bukzor)
I really don't know what these mean, but I'm fairly sure they're not my fault.
I'm on revision f9d87b7d36ed (bb).
The text was updated successfully, but these errors were encountered: