Not having configuration settings such as EOSIO_S2WASM and EOSIO_WAST2WASM
caused cryptic error messages when forming a commandline with that as
the executable, such as, "expect bytes or str, not NoneType".
Hi, thanks for this PR. We'll close this PR without merging, as we believe that due to the changes introduced in the upcoming 2.2 release this issue is no longer relevant.
Not having configuration settings such as EOSIO_S2WASM and EOSIO_WAST2WASM caused cryptic error messages when forming a commandline with that as the executable, such as, "expect bytes or str, not NoneType".
Closes #71