A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/adobe-type-tools/afdko/issues/417 below:

makeotf always exits with 0 (i.e. success) even when error occurs · Issue #417 · adobe-type-tools/afdko · GitHub

The MakeOTF.py script's main() function does not return a non-zero value to the calling shell when an exception occurs and the font was not built successfully. Currently all exceptions are handled and passed, so main always exits successfully:

except (MakeOTFOptionsError, MakeOTFTXError, MakeOTFRunError): pass except Exception: import traceback traceback.print_exc() finally: if not makeOTFParams.debug: for tempPath in makeOTFParams.tempPathList: if os.path.exists(tempPath): os.remove(tempPath) print("Done.")

in fontmake there's an optional FDKFeatureCompiler that calls makeotf as subprocess. That code is broken for many reasons, one of which is that it attempts to guess whether the build was successful from the messages printed to stdout, because the exit code is meaningless.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4