FIX - Passing compiled modules to traceback_exclude_modules #119
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Configure.traceback_exclude_modules
receives a list of modules, and extracts the__file__
of each, allowing to skip few modules from appearing in the stacktrace.In Python 2.x, when a compiled module is loaded, it's
__file__
property displays the compiled.pyc
path, while the running code will appear in the stacktrace with a.py
suffix.This fix replaces the .pyc suffix with a .py, hence enabling the
traceback_exclude_modules
to work as it should.I also added tests reproducing this scenario, and also tweaked .travis.yml to support the new image they deployed recently (https://blog.travis-ci.com/2017-05-04-precise-image-updates).