[issue15486] Standardised mechanism for stripping importlib frames from tracebacks

[Nick Coghlan]

Nick Coghlan added the comment:

In trying to find a new case that wasn't already covered by the test suite, I found an error which I'm not even sure should be an error. Doesn't 3.2 suppress failures that occur when attempting to implicitly cache the .pyc?

Anyway, given the rest of the patch, trimming this traceback will be easy if we decide that's the right thing to do.

----------
components: +Interpreter Core, Library (Lib)
keywords: +patch
nosy: +amaury.forgeotdarc, brett.cannon, eric.snow, georg.brandl
priority: normal -> release blocker
stage:  -> patch review
title: Standardise the mechanisms for stripping importlib frames -> Standardised mechanism for stripping importlib frames from tracebacks
type:  -> behavior
versions: +Python 3.3
Added file: http://bugs.python.org/file26573/issue15486_simplify_importlib_frame_removal.diff

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue15486>
_______________________________________