Description:
mysqlworkbench is not working in OSX 10.14.6 it fails like this:
/Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
Your PYTHONPATH points to a site-packages dir for Python 3.x but you are running Python 2.x!
PYTHONPATH is currently: "/Applications/MySQLWorkbench.app/Contents/Resources/libraries"
You should `unset PYTHONPATH` to fix this.
The only python installed in the system is the default one.
/Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench --log-level debug3 --log-to-stderr
Logger set to level 'debug3'. '1111111'
18:41:20 [INF][ WBContext]: Logger set to level 'debug3'
18:41:20 [DB1][ Workbench]: Initializing mforms
18:41:20 [DB2][ mforms backend]: Initializing mforms factory
18:41:20 [DB1][ WBContext]: Creating WBContext
18:41:20 [INF][ WBContext UI]: Initializing workbench context UI with these values:
base dir: /Applications/MySQLWorkbench.app/Contents/Resources
plugin path: /Applications/MySQLWorkbench.app/Contents/PlugIns
struct path: /Applications/MySQLWorkbench.app/Contents/Resources/grt
module path: /Applications/MySQLWorkbench.app/Contents/PlugIns:/Applications/MySQLWorkbench.app/Contents/Resources/plugins
library path: /Applications/MySQLWorkbench.app/Contents/Resources/libraries
user data dir: /Users/andresmmujica/Library/Application Support/MySQL/Workbench
open at start:
open type:
run at startup:
run type:
Force SW rendering: No
Force OpenGL: No
quit when done: No
18:41:20 [INF][ WBContext]: WbContext::init
18:41:20 [DB1][ GRTDispatcher]: starting worker thread
18:41:20 [DB1][ GRTDispatcher]: worker thread running
Your PYTHONPATH points to a site-packages dir for Python 3.x but you are running Python 2.x!
PYTHONPATH is currently: "/Applications/MySQLWorkbench.app/Contents/Resources/libraries"
You should `unset PYTHONPATH` to fix this.
How to repeat:
Install MYSQLWB in a clean install of MacOS Mojave
Suggested fix:
I've tried a lot of stuff, so that's why I'm here. I suspect it uses hardcoded python path and sets the pythonpath to it's own libraries.
As the default python is 2.7 and the libraries are 3.x that's why it fails. I cannot remove default python.
Description: mysqlworkbench is not working in OSX 10.14.6 it fails like this: /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench Your PYTHONPATH points to a site-packages dir for Python 3.x but you are running Python 2.x! PYTHONPATH is currently: "/Applications/MySQLWorkbench.app/Contents/Resources/libraries" You should `unset PYTHONPATH` to fix this. The only python installed in the system is the default one. /Applications/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench --log-level debug3 --log-to-stderr Logger set to level 'debug3'. '1111111' 18:41:20 [INF][ WBContext]: Logger set to level 'debug3' 18:41:20 [DB1][ Workbench]: Initializing mforms 18:41:20 [DB2][ mforms backend]: Initializing mforms factory 18:41:20 [DB1][ WBContext]: Creating WBContext 18:41:20 [INF][ WBContext UI]: Initializing workbench context UI with these values: base dir: /Applications/MySQLWorkbench.app/Contents/Resources plugin path: /Applications/MySQLWorkbench.app/Contents/PlugIns struct path: /Applications/MySQLWorkbench.app/Contents/Resources/grt module path: /Applications/MySQLWorkbench.app/Contents/PlugIns:/Applications/MySQLWorkbench.app/Contents/Resources/plugins library path: /Applications/MySQLWorkbench.app/Contents/Resources/libraries user data dir: /Users/andresmmujica/Library/Application Support/MySQL/Workbench open at start: open type: run at startup: run type: Force SW rendering: No Force OpenGL: No quit when done: No 18:41:20 [INF][ WBContext]: WbContext::init 18:41:20 [DB1][ GRTDispatcher]: starting worker thread 18:41:20 [DB1][ GRTDispatcher]: worker thread running Your PYTHONPATH points to a site-packages dir for Python 3.x but you are running Python 2.x! PYTHONPATH is currently: "/Applications/MySQLWorkbench.app/Contents/Resources/libraries" You should `unset PYTHONPATH` to fix this. How to repeat: Install MYSQLWB in a clean install of MacOS Mojave Suggested fix: I've tried a lot of stuff, so that's why I'm here. I suspect it uses hardcoded python path and sets the pythonpath to it's own libraries. As the default python is 2.7 and the libraries are 3.x that's why it fails. I cannot remove default python.