On Thursday February 05 2015 20:57:53 André Pönitz wrote: Hi André
> > I haven't looked at the Creator code for a while, but doesn't it launch > > Python with a .py file? > > Not anymore. Ok, from what version if I may ask? > Invoking sys.executable inside LLDB does not reliably produce a Python > executable usable with that LLDB. Not even on Linux. This probably more a question to ask on the lldb ML, but that surprises me more than just a bit. My OS X lldb (inside the Xcode bundle) is linked against /Applications/Xcode.app/Contents/SharedFrameworks/LLDB.framework/LLDB, which in turn is linked against /System/Library/Frameworks/Python.framework/Versions/2.7/Python . So that's the python it should be loading when it starts an embedded interpreter. I see that that interpreter indeed gives a sys.path that includes the paths from my MacPorts python-2.7 , which I never realised was possible. Interestingly sys.version is unchanged though... > The point of invoking LLDB first is to not have to care where its Python > support infrastructure lives. No argument there, it makes sense, and means this thread came too late (pending verification, though ;)). R. _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
