[wingide-users] Mac OSX, Python framework, and netserver module exceptionMorgen Sagen morgen at osafoundation.org
Thu, 13 Feb 2003 11:19:31 -0800
Thanks for investigating this. I remembered that the OSX dynamic loader pays attention to various environment variables to alter its behavior, and found that by specifying DYLD_FORCE_FLAT_NAMESPACE=1 before launching wing, those missing symbols are made visible. I'm not sure if this is a great solution, but it seemed to work. See http://www.hmug.org/man/1/dyld.html My new problem to investigate is that when you build python with framework support, you actually end up with two python executables: one in Frameworks/Python.framework/Versions/Current/bin and one in Applications/Python.app/contents/MacOS. The latter is able to run wxPython apps, but doesn't accept more than one command-line argument (which means wing can't spawn it correctly), and the former accepts command-line arguments but wxPython scripts run using it don't receive mouse events. So neither python executable works for what I need. I'm off to go figure this one out. ~morgen On Thursday, February 13, 2003, at 10:32 AM, Wing IDE Support wrote: > It looks like the problem is that there's two separate Python versions > on the Mac: python built with framework support (sometimes referred to > as MacPython) and python without framework support (sometimes referred > to as unix-python). Extension modules built with one of these versions > evidently will not work with the other version because of differences > in > how the shared library symbols are resolved. > > We are investigating this problem and will probably release a patch for > Wing that contains the extension modules built for MacPython as well as > the modules for unix-python. > > John > > On Wed, 2003-02-12 at 16:56, Morgen Sagen wrote: >> What works: >> >> Using the python that ships with OSX, wing can successfully debug a >> simple one-line python script (print "foo"). >> >> What doesn't: >> >> Using a Python-2.2.2 framework that we have built ourselves, wing >> times >> out when trying to debug the same script (displays the "Connection >> Failed" dialog). It also looks like the spawned wingdb is dying >> silently. >> >> What I found: >> >> I added a traceback dump to wingdb.py to see what was going on, and in >> CreateErrStream() the call to netserver.abstract.CErrStream() throws >> the >> following exception... >> >> 'module' object has no attribute 'abstract' >> >> Does anyone know what could be causing this problem? >> >> Thanks, >> ~morgen >> >> _________________________________________________ >> Wing IDE discussion list >> http://wingide.com/support/forum > > >
Run by Mailman v 2.0.8
Copyright (c) 2000-2002, Archaeopteryx Software, Inc.