[issue22280] _decimal: successful import despite build failure

Stefan Krah added the comment: Ah nice, let's continue with your issue then. -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> The Modules/ directory should not be added to sys.path ___ Python tracker

[issue22280] _decimal: successful import despite build failure

STINNER Victor added the comment: Oh, it looks like I opened a similar issue: #22285 (with a patch). -- nosy: +haypo ___ Python tracker ___ __

[issue22280] _decimal: successful import despite build failure

Stefan Krah added the comment: The effect can also be seen on the two buildbots that currently fail to build _decimal due to a libmpdec version mismatch: http://buildbot.python.org/all/builders/AMD64%20Fedora%20without%20threads%203.x/builds/7088/steps/test/logs/stdio -- keywords: +buil

[issue22280] _decimal: successful import despite build failure

New submission from Stefan Krah: This may be related to PEP 451: Previously, if the _decimal.so build failed for whatever reason, decimal.py would be used instead. For that to work, importing _decimal needs to fail. But now the import is successful: # Simulate build failure: rm Modules/_decima