> Okay, mystery solved. A bogus PYTHONHOME environment variable > was defined. > > (I had installed an application that used python on a removable drive. > I was one of those download and run a small web-installer application, > so I never really knew what the install process entailed. It defined > PYTHONHOME pointing to the generally absent removable drive, a > detail I hadn't noticed. > > Why not just "download this file and unzip it into a directory of your > choice, and define the following environment variable to point to that > directory"? You know, kind of like mingw-w64 does...) > > Anyway, I removed (renamed, actually) the PYTHONHOME variable, > and now gdb works just fine. Although having gdb break because of > the bad PYTHONHOME variable does seem a little fragile. > >
Have you had a chance to play with http://pypi.python.org/pypi/virtualenvand http://pypi.python.org/pypi/pip Jon --- http://thecodeshop.github.com | http://jonforums.github.com/ twitter: @jonforums
------------------------------------------------------------------------------ Get your Android app more play: Bring it to the BlackBerry PlayBook in minutes. BlackBerry App World™ now supports Android™ Apps for the BlackBerry® PlayBook™. Discover just how easy and simple it is! http://p.sf.net/sfu/android-dev2dev
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
