> > > > However, it still doesn't work for the OP of #8925. 5 days ago, he > > couldn't find a "patched" dmg. I don't know what is patched, but are > > you still sure the new package doesn't work on his machine ? > > The OP had python3 from macports installed. > > The path_prefix of LyX on Mac sets /opt/local/bin before /usr/bin and > therefor LyX was using python3 instead of the python2 in /usr/bin. > LyX wasn't able to configure itself and no window were opened. > > This opens some questions: > * Why is /opt/local/bin in path_prefix? > * Why is there no feedback given for automatic initial configure run? > * Why is there no feedback given for a failure with this configure run? > * What should be done to prevent this scenario? > > I'd cleanup the path_prefix in development/MacOSX/lyxrc.dist.in and > let the OP try the resulting package. > I have another question (this was what I was trying to fix also): - why the python2() code in os.cpp (line 41) does not prevent the wrong python to be selected. In particular, why is the test out.first < 0 and not out.first != 0 ?
This would have prevented the python3 version from being selected. Benjamin
