You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2024. It is now read-only.
Raising this issue for anyone who installed python3 with homebrew and then installed mssql-scripter following these instructions.
If you ever run into the error something like this. This is caused by an mismatch in the mssql-script bin file.
/opt/homebrew/bin/mssql-scripter: line 16: python: command not found
To fix this I found that editing the mssql-scripter file, which was created in:
/opt/homebrew/bin/,
and change the bottom line to use the python3 executable instead of python, changing this:
python -m mssqlscripter "$@"
to:
python3 -m mssqlscripter "$@"
Is there any way for the mssql-scripter file to check someones python version before executing either python or python3.
The text was updated successfully, but these errors were encountered:
No usable version of the libssl was found
Scripting request: 1 encountered error: Scripting request encountered a exception
Error details: ('End of stream reached, no output.',)
No usable version of the libssl was found
Scripting request: 1 encountered error: Scripting request encountered an exception
Error details: ('End of stream reached, no output.',)
OS: Mac OS Ventura
Python: Python3
Raising this issue for anyone who installed python3 with homebrew and then installed mssql-scripter following these instructions.
If you ever run into the error something like this. This is caused by an mismatch in the mssql-script bin file.
/opt/homebrew/bin/mssql-scripter: line 16: python: command not found
To fix this I found that editing the mssql-scripter file, which was created in:
/opt/homebrew/bin/
,and change the bottom line to use the python3 executable instead of python, changing this:
python -m mssqlscripter "$@"
to:
python3 -m mssqlscripter "$@"
Is there any way for the mssql-scripter file to check someones python version before executing either python or python3.
The text was updated successfully, but these errors were encountered: