Python module import issues in command prompt?

You're running two different Python installs, one dated 10/4/2011 and the other dated 11/28/2011. The second one doesn't have whoosh installed.

You're running two different Python installs, one dated 10/4/2011 and the other dated 11/28/2011. The second one doesn't have whoosh installed. Your options are: Look for the version that IDLE uses and run it from the command-line.To find it, turn on IDLE and run import sys; print sys.executable.

That will show you the location of the version with the packages installed. Or you can beef-up your command-line version by installing those same packages at the command-line (i.e. Run python setup.

Py install for the various packages you want to load.

Packages are searched in all the directories defined in the python path. So, if the IDLE and terminal are working differently - means they have difference in their python paths. So, Try this : (On both IDLE and terminal) import sys print sys.

Path # this prints the list of directories in the python path. Compare the list that you get from both and the extra directory in IDLE will be having whoosh You can add directories to sys. Path like this : import sys sys.path.

Append('/home/user/packages') Now, all packages in /home/user/packages will be available for import.

This generally happens when you have different python installations, so different sys. Path and when you install a new package that gets installed to one of your python installations. – Yugal Jindle Nov 30 '11 at 4:35 This works, but only temporarily (in my experience).

Setting PYTHONPATH will make terminal always have the modules available. – Jon Nov 30 '11 at 4:36 I know that would be better - but by this I want him to see what's causing the problem. – Yugal Jindle Nov 30 '11 at 4:38 @YugalJindle, you are right.

How do I remove terminal version and make it point to IDLE version. If I use apt-get remove python, I am not sure which version will get deleted? – Pradeep Nov 30 '11 at 4:49 I would have removed both.. and then reinstalled the one that I wanted to have.

That is the best thing when you want to save time from troubleshooting - When there is nothing to loose. – Yugal Jindle Nov 30 '11 at 5:04.

You need to make sure PYTHONPATH is set correctly in your ~/. Profile or /usr//.profile. For example (this is for OS X, but just find where Python is installed on your machine): export PYTHONPATH="/usr/local/lib/python2.7/site-package/:$PYTHONPATH" Only OS X requires the export prefix, and you can check your current path using echo $PYTHONPATH in terminal.

Once you've changed PYTHONPATH to point to your version of python's package folder, you need to force terminal to update the path using this: source ~/. Profile Then try echo $PYTHONPATH again and make sure it changed. Then you should be set as long as you pointed to the correct directory.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.