On Sep 16, 7:49 pm, DavidFawcett <[email protected]> wrote: > On my work machine, I have a primary Python 2.5 install that is used > by some applications and I run code with it. > > I also have a second install of Python that is part of a suite of > OpenSource Geospatial apps (OSGeo4W). When I want to write and run > Python code against that instance of Python, I currently write the > code in an editor and then run it from the command prompt. OSGeo4W > launches a shell window configured to point to its own Python > install. > > I am putting together a workshop and I would like the students to be > able to use an IDE to write and run the OpenSource code too. > > Is there a configuration or installation setting to point spyder to > the 'non-primary' Python. I tried installing spyder in the site- > packages of the 'non-primary' Python install, but when looking at the > install log, many things were installed in the 'primary-python' > location. I am guessing that the installer is looking at the registry > settings.
You will have to install Spyder on the 'non-primary' Python install indeed, but not by executing the Python(x,y) installer because it is partly relying on registry entries. The cleanest way to install Spyder on the 'non-primary' Python install is installing from source code: 'python setup.py install' -- of course you will have to be sure that the 'python' executable used in this command is the 'non-primary' one. Pierre > Both installs are Python 2.5, so I suppose that there is some > potential for just adjusting PYTHONPATH to run the 'non-primary' > modules through the 'primary' interpreter... > > Any help is appreciated. > > David. -- You received this message because you are subscribed to the Google Groups "spyder" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/spyderlib?hl=en.
