Open transmissions11 opened 2 years ago
temporary workaround is to set the vyper command to arch -x86_64 vyper
hey @transmissions11,
sorry for the late reply. yeah, the default vyper command is set to vyper
(whatever your system-wide vyper command is configured for) and it's executed using child_process.exec()
which spawns /bin/sh
by default.
I suggest documenting this for now unless this is an issue for more people. Open to other way to fix this. In general, the vyper.command
can be anything, including a shell invocation, however, setting the arch before launching vyper may be the best way forward for now. Another idea would be to force exec()
to use env.SHELL
(instead of the default /bin/sh
) assuming that your default shell is set up correctly to execute vyper. However, I would like to avoid adding code that has to auto-figure user envs :)
hope that helps. added a note to the readme (https://github.com/tintinweb/vscode-vyper/pull/24/commits/1bac179b0bb5b5de013025cb5b9c5b5d215a9467).
cheers, tin
Compiling the Example ERC20 works just fine via the cli, but when I save in the vscode it fails with this message:
i believe this is because my terminal runs in rosetta mode but vscode will run
vyper
raw? is there a way i can get the extension to use rosetta as well